From: Antti Tuominen <ajtuomin@morphine.tml.hut.fi>
To: Pekka Savola <pekkas@netcore.fi>
Cc: davem@redhat.com, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org, yoshfuji@wide.ad.jp,
torvalds@transmeta.com, jagana@us.ibm.com
Subject: Re: [PATCHSET] Mobile IPv6 for 2.5.43
Date: Fri, 18 Oct 2002 10:39:17 +0300 [thread overview]
Message-ID: <20021018073917.GA19020@morphine.tml.hut.fi> (raw)
In-Reply-To: <Pine.LNX.4.44.0210172309160.28084-100000@netcore.fi>
On Thu, Oct 17, 2002 at 11:14:32PM +0300, Pekka Savola wrote:
> On Thu, 17 Oct 2002, Antti Tuominen wrote:
> > Intermediate revision of the specification "Draft 18++" appeared a few
> > days ago, which addressed most of the issues with earlier drafts (16,
>
> Sounds great. Hopefully it slows down a bit from being a moving target.
I heard Draft 19 should be out next week, so that should consolidate
the MIPv6 effort even further.
> 1) current tunneling (including sanity checks which are, I believe, a bit
> non-existant at the moment) should be generalized to handle v6-in-v6 and
> v6-in-v4 tunneling anyway. Not sure if this is the right way, but that's
> IMO one priority item.
I'm sure we can improve the v6-in-v6 tunnel. We had some discussion
with USAGI people about doing anything-in-v6 general tunnel, but since
that is somewhat beyond our project scope, v6-in-v6 is all we can
offer at this time. I don't know about the USAGI folks' status on
this.
> 2) without IPSEC, there is no way to secure MN-HA traffic. Therefore I
> think the first priority is being able to support Correspondent Node
> behaviour.
Right. We've had our own IPSec AH support in all the previous
releases, but as everyone probably knows the USAGI guys have
implemented IPv6 IPSec. This is why we dropped the IPSec stuff in our
code. There is no point doing the same work again. If (or when)
USAGI IPSec gets accepted to the kernel, we will be sure to modify our
code to support it.
> Having IPSEC + MIPv6 in 2.6 series would be Really Cool, though :-)
This is something we're hoping for too.
Regards,
Antti
--
Antti J. Tuominen, Gyldenintie 8A 11, 00200 Helsinki, Finland.
Research assistant, Institute of Digital Communications at HUT
work: ajtuomin@tml.hut.fi; home: tuominen@iki.fi
next prev parent reply other threads:[~2002-10-18 7:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 16:26 [PATCHSET] Mobile IPv6 for 2.5.43 Antti Tuominen
2002-10-17 17:18 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-17 17:56 ` Mitsuru KANDA
2002-10-18 11:16 ` Antti Tuominen
2002-10-17 23:52 ` Ville Nuorvala
2002-10-18 0:56 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-17 20:14 ` Pekka Savola
2002-10-18 7:39 ` Antti Tuominen [this message]
2002-10-17 22:51 ` Ville Nuorvala
2002-10-31 8:44 ` Noriaki Takamiya
2002-10-31 8:55 ` Pekka Savola
2002-10-31 9:08 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-31 10:41 ` Antti Tuominen
2002-11-01 3:27 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-31 10:44 ` Henrik Petander
2002-11-01 3:22 ` YOSHIFUJI Hideaki / 吉藤英明
-- strict thread matches above, loose matches on Subject: below --
2002-10-17 17:22 Krishna Kumar
2002-10-17 21:57 ` Ville Nuorvala
2002-10-17 17:46 Krishna Kumar
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=20021018073917.GA19020@morphine.tml.hut.fi \
--to=ajtuomin@morphine.tml.hut.fi \
--cc=davem@redhat.com \
--cc=jagana@us.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
--cc=torvalds@transmeta.com \
--cc=yoshfuji@wide.ad.jp \
/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).