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: [PATCH 0/23][XFRM] MIPv6 CN introduction (part A) (Re: [RFC] Mobile IPv6 introduction)
Date: Sat, 29 Jul 2006 18:28:13 +0900 [thread overview]
Message-ID: <44CB2A2D.4090808@linux-ipv6.org> (raw)
In-Reply-To: <44CB2914.9010803@linux-ipv6.org>
Please see patches about "Avanced XFRM for CN", following this mail.
These are just for review, and it is against 2.6.17.
"Avanced XFRM for CN" tree is consists of:
A. XFRM extension for route optimization
B. IPv6 extension headers:
new type (2) of routing header
new TLV option for destination options header: home address option
new header for signaling: mobility header
Part B patches depend on A. Let me start part A first.
Part A is also available as mip6cn-20060716-review branch at:
git://git.skbuff.net:9419/gitroot/nakam/linux-2.6-mip6cn-xfrm
> 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.
--
Masahide NAKAMURA
next prev parent reply other threads:[~2006-07-29 9:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 9:23 [RFC] Mobile IPv6 introduction Masahide NAKAMURA
2006-07-29 9:28 ` Masahide NAKAMURA [this message]
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=44CB2A2D.4090808@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 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.