From: Masahide NAKAMURA <nakam@linux-ipv6.org>
To: davem@davemloft.net
Cc: yoshfuji@linux-ipv6.org, anttit@tcs.hut.fi, vnuorval@tcs.hut.fi,
netdev@vger.kernel.org, usagi-core@linux-ipv6.org
Subject: [RFC] Mobile IPv6 introduction
Date: Sat, 29 Jul 2006 18:23:32 +0900 [thread overview]
Message-ID: <44CB2914.9010803@linux-ipv6.org> (raw)
Hello,
Let me introduce Mobile IPv6(RFC3775) patch and its outline.
We USAGI project and HUT Go/Core project have developed
for Mobile IPv6(MIPv6) stack on 2.6 tree as MIPL2 for several years.
Our aim is to make kernel patch smaller (than MIPL1 which is for
2.4 kernel).
We find out we have 4 categories for the patch:
1. IPv6 policy routing
2. IPsec MIGRATE
3. Advanced XFRM for Correspondent Node(CN)
4. MISC
3, 4 are MIPv6 specific feature but 1, 2 are not.
It can be discussed in parallel about 1, 2, 3 because they
don't depend on others.
1. IPv6 policy routing
Thomas and Yoshifuji have already started to discuss and work for it.
This is required by Mobile Node(MN) and used by Home Agent(HA).
2. IPsec MIGRATE
This is an interface to update IPsec end-point address of SAD/SPD.
(there is an IETF draft: draft-sugimoto-mip6-pfkey-migrate-XX)
This is required by MN and HA to use IPsec tunnel.
3. Advanced XFRM for CN
"Route optimization" defined MIPv6 specification
is designed as XFRM extension. IPv6 extension headers
handling is included, too.
This feature is required by all MIPv6 nodes(CN, MN, HA) then it can
be said MIPv6 platform.
4. MISC
This is a set of small patches but works with the above categories
since they are finally confirmed as the MIPv6 node behavior;
e.g. home addressing for MN, proxy forwarding for HA.
At first I'll send patches about category "3" very soon, just for review.
Can you check them?
Thanks,
--
Masahide NAKAMURA
next reply other threads:[~2006-07-29 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 9:23 Masahide NAKAMURA [this message]
2006-07-29 9:28 ` [PATCH 0/23][XFRM] MIPv6 CN introduction (part A) (Re: [RFC] Mobile IPv6 introduction) Masahide NAKAMURA
2006-07-29 9:37 ` [PATCH 0/20][IPV6/XFRM] MIPv6 CN (part B) Masahide NAKAMURA
2006-08-02 0:30 ` David Miller
2006-08-02 8:26 ` Masahide NAKAMURA
2006-07-29 14:12 ` [RFC] Mobile IPv6 introduction Hugo Santos
2006-08-02 0:35 ` David Miller
2006-08-02 0:58 ` Hugo Santos
2006-08-02 1:04 ` David Miller
2006-08-02 1:52 ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-02 7:58 ` Ville Nuorvala
2006-08-02 11:03 ` Hugo Santos
2006-08-02 3:24 ` Masahide NAKAMURA
2006-08-02 10:47 ` Hugo Santos
2006-08-02 13:03 ` Masahide NAKAMURA
2006-08-02 21:14 ` David Miller
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=44CB2914.9010803@linux-ipv6.org \
--to=nakam@linux-ipv6.org \
--cc=anttit@tcs.hut.fi \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=usagi-core@linux-ipv6.org \
--cc=vnuorval@tcs.hut.fi \
--cc=yoshfuji@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).