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: Sat, 03 Feb 2007 08:45:57 -0500 [thread overview]
Message-ID: <1170510358.3979.4.camel@localhost> (raw)
In-Reply-To: <20070203085225.E309.SHINTA@sfc.wide.ad.jp>
On Sat, 2007-03-02 at 09:28 +0900, Shinta Sugimoto wrote:
> Yes. A XFRM_MSG_MIGRATE message can update an SPD entry and associated
> SAD entries (if any) at a time.
>
Ok, you have convinced me on the need for the message.
> By "Mobile VPN", I meant a VPN scenario where clients roam around
> subnets and continue changing its attachment point to the Internet
> (aka roadwarrior). In such case, both client and SGW need to update
> endpoint address of the security association. When the endpoint address
> of client side is updated, instead of re-establishing the security
> association from scratch, the client may inform the SGW of its new
> endpoint address. This is what MOBIKE (RFC4555) does. So, just like
> in the case of Mobile IPv6, endpoint address management of IPsec
> databases is necessary and XFRM_MSG_MIGRATE message can be used.
makes a lot of sense.
Thanks for your patience Shinta.
cheers,
jamal
next prev parent reply other threads:[~2007-02-03 13:46 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
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 [this message]
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=1170510358.3979.4.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.