From: Henrik Petander <lpetande@tml.hut.fi>
To: Masahide NAKAMURA <nakam@linux-ipv6.org>
Cc: "David S. Miller" <davem@redhat.com>,
lpetande@morphine.tml.hut.fi, yoshfuji@linux-ipv6.org,
vnuorval@tcs.hut.fi, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com,
ajtuomin@morphine.tml.hut.fi, jagana@us.ibm.com,
kumarkr@us.ibm.com, usagi-core@linux-ipv6.org
Subject: Re: [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6
Date: Fri, 13 Jun 2003 17:27:50 +0300 [thread overview]
Message-ID: <3EE9DF66.1090409@tml.hut.fi> (raw)
In-Reply-To: <20030613202652.1d64ed6f.nakam@linux-ipv6.org>
Masahide NAKAMURA wrote:
> On Thu, 12 Jun 2003 11:44:49 +0300
> Henrik Petander <lpetande@tml.hut.fi> wrote:
>>
>>I don't see a problem in that. It would only result in a short period of
>>missing mipv6 route optimization information, until MIPv6 daemon
>>reinserted the mipv6 information. MIPv6 daemon would do this after
>>getting a notification of the deletion of the old mipv6 related cached
>>routes. This would relate to zebra in the same way as pmtu discovery.
>
>
> When routing information is deleted by zebra, the packets from user
> application will be sent incorrectly until MIPv6 daemon re-inserts
> the special host route.
The packets between Mobile Node and Correspondent Node would be just
sent through the tunnel via Home Agent. Only parts of the direct traffic
between MN and HA would be temporarily lost. Since HA is conceptually a
router, the traffic between MN and HA should be very limited and Mobile
IP / IPSec signaling would not be affected. This is why IMO the use of
soft state is acceptable.
> How about making new policy(MIPv6 policy) in the similar way of IPsec?
> MIPv6 and IPsec policy are managed by separated list.
It would be a good solution from our POV, since it should work well with
IPSec.
Regards,
Henrik
next prev parent reply other threads:[~2003-06-13 14:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030424132559.GA15894@morphine.tml.hut.fi>
2003-05-30 14:34 ` [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6 Ville Nuorvala
2003-05-30 15:00 ` [patch]: ipv6 tunnel " Ville Nuorvala
2003-05-30 15:38 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-04 4:38 ` David S. Miller
2003-06-04 14:30 ` Henrik Petander
2003-06-04 15:49 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-04 17:31 ` Henrik Petander
2003-06-05 8:36 ` Ville Nuorvala
2003-06-05 12:40 ` Ville Nuorvala
2003-06-04 4:34 ` David S. Miller
2003-06-04 12:40 ` Ville Nuorvala
2003-06-07 10:30 ` David S. Miller
2003-06-07 10:41 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-09 11:43 ` ipv6 tunnel patch (was: Re: [patch]: ipv6 tunnel for MIPv6) Ville Nuorvala
2003-06-09 14:55 ` ipv6 tunnel patch David S. Miller
2003-05-30 15:03 ` [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6 YOSHIFUJI Hideaki / 吉藤英明
2003-05-30 20:38 ` Venkata Jagana
2003-06-03 6:35 ` Ville Nuorvala
2003-06-05 10:12 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-06 5:38 ` Masahide NAKAMURA
2003-06-06 11:14 ` Henrik Petander
2003-06-06 13:31 ` Masahide NAKAMURA
2003-06-09 9:06 ` Henrik Petander
2003-06-09 11:37 ` Masahide NAKAMURA
2003-06-10 15:25 ` Henrik Petander
2003-06-10 15:40 ` Masahide NAKAMURA
2003-06-10 16:56 ` David S. Miller
2003-06-10 16:51 ` David S. Miller
2003-06-11 8:48 ` Henrik Petander
2003-06-12 3:20 ` David S. Miller
2003-06-12 8:44 ` Henrik Petander
2003-06-12 8:49 ` David S. Miller
2003-06-13 11:26 ` Masahide NAKAMURA
2003-06-13 14:27 ` Henrik Petander [this message]
2003-06-06 8:48 ` Ville Nuorvala
2003-06-06 10:32 ` CONFIG_IPV6_SUBTREES (was [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6) YOSHIFUJI Hideaki / 吉藤英明
2003-06-06 11:16 ` Ville Nuorvala
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=3EE9DF66.1090409@tml.hut.fi \
--to=lpetande@tml.hut.fi \
--cc=ajtuomin@morphine.tml.hut.fi \
--cc=davem@redhat.com \
--cc=jagana@us.ibm.com \
--cc=kumarkr@us.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=lpetande@morphine.tml.hut.fi \
--cc=nakam@linux-ipv6.org \
--cc=netdev@oss.sgi.com \
--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).