From: jamal <hadi@cyberus.ca>
To: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
Cc: netdev@vger.kernel.org,
Francis Dupont <Francis.Dupont@point6.net>,
Masahide Nakamura <nakam@linux-ipv6.org>,
usagi-core@linux-ipv6.org
Subject: Re: [RFC][PATCH][XFRM][0/5] extension for XFRM databases
Date: Thu, 01 Feb 2007 08:24:33 -0500 [thread overview]
Message-ID: <1170336273.3915.12.camel@localhost> (raw)
In-Reply-To: <20070201114339.E2BD.SHINTA@sfc.wide.ad.jp>
Hello,
I think i may have understood your approach before but i am a little
lost right now, so bear with me.
Could we not achieve your goals by using (on XFRM at least)
XFRM_MSG_UPDPOLICY and XFRM_MSG_UPDSA ?
cheers,
jamal
On Thu, 2007-01-02 at 13:09 +0900, Shinta Sugimoto wrote:
> Hello,
>
> Let me issue a request for comments for the patch set developed by
> the USAGI project. The patch set aims to extend the XFRM framework
> so that endpoint addresses in the XFRM databases, namely Could XFRM policy
> and XFRM state can be dynamically updated according to a request from
> user application. This feature is required for Mobile IPv6 to follow
> the security requirements specified in RFC3776. More specifically,
> the Mobile Node and Home Agent need to update the endpoint addresses
> of the IPsec tunnel when the Mobile Node changes its attachment point
> (Care-of Address) to the Internet. The kernel also notifies userland
> application via both Netlink and PF_KEY sockets so that user application
> (e.g. IKE Daemon) could be informed of the updates appropriately.
> More detailed information of motivation/rationale for this feature
> can be found in the internet draft[1].
>
> The patch set consists of following patches:
>
> [1/5] [XFRM]: Extension to the XFRM framework for dynamic update of endpoint address(es)
> [2/5] [XFRM]: User interface for handling XFRM_MSG_MIGRATE
> [3/5] [XFRM]: CONFIG_XFRM_MIGRATE option
> [4/5] [PFKEYV2]: Extension to the PF_KEYv2 framework for dynamic update of endpoint address(es)
> [5/5] [PFKEYV2]: CONFIG_NET_KEY_MIGRATE option
>
> Any comments/suggestions are appreciated.
> Thank you very much.
>
> [1]: http://www.ietf.org/internet-drafts/draft-sugimoto-mip6-pfkey-migrate-03.txt
>
>
> Regards,
> Shinta
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-02-01 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 4:09 [RFC][PATCH][XFRM][0/5] extension for XFRM databases Shinta Sugimoto
2007-02-01 13:24 ` jamal [this message]
2007-02-02 11:25 ` Shinta Sugimoto
2007-02-02 13:35 ` jamal
2007-02-03 0:28 ` Shinta Sugimoto
2007-02-03 13:45 ` jamal
2007-02-05 0:56 ` David Miller
2007-02-05 1:15 ` Shinta Sugimoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1170336273.3915.12.camel@localhost \
--to=hadi@cyberus.ca \
--cc=Francis.Dupont@point6.net \
--cc=nakam@linux-ipv6.org \
--cc=netdev@vger.kernel.org \
--cc=shinta@sfc.wide.ad.jp \
--cc=usagi-core@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.