Re: [Monami6] Simultaneous location in home and foreign
Benjamin Koh <benjamin.kohtm@sg.panasonic.com> Fri, 09 December 2005 08:29 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkddM-00058a-In; Fri, 09 Dec 2005 03:29:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkddK-00057I-Gq for monami6@megatron.ietf.org; Fri, 09 Dec 2005 03:29:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00098 for <monami6@ietf.org>; Fri, 9 Dec 2005 03:28:45 -0500 (EST)
Received: from smtp.mei.co.jp ([133.183.129.25] helo=smtp1.mei.co.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkddR-0001sw-7x for monami6@ietf.org; Fri, 09 Dec 2005 03:29:47 -0500
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150]) by smtp1.mei.co.jp (8.12.10/3.7W/jazz) with ESMTP id jB98T5fn029063 for <monami6@ietf.org>; Fri, 9 Dec 2005 17:29:05 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx3) with ESMTP id jB98T8Q24051 for <monami6@ietf.org>; Fri, 9 Dec 2005 17:29:08 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1]) by mail.jp.panasonic.com (8.11.6p2/3.7W/bluejays) with ESMTP id jB98T7P21268 for <monami6@ietf.org>; Fri, 9 Dec 2005 17:29:07 +0900 (JST)
Received: from [10.68.136.71] ([10.68.136.71]) by pslexc01.psl.local with Microsoft SMTPSVC(6.0.3790.1830); Fri, 9 Dec 2005 16:29:04 +0800
Message-ID: <43994062.40800@sg.panasonic.com>
Date: Fri, 09 Dec 2005 16:29:22 +0800
From: Benjamin Koh <benjamin.kohtm@sg.panasonic.com>
User-Agent: Thunderbird 1.4.1 (X11/20051006)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] Simultaneous location in home and foreign
References: <A11736FE943F1A408F8BBB1B9F5FE8AD03274ACD@ftmailserver.flariontech.com> <438FA5B1.9050706@sg.panasonic.com> <m2k6eflahr.wl%ryuji@sfc.wide.ad.jp>
In-Reply-To: <m2k6eflahr.wl%ryuji@sfc.wide.ad.jp>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Dec 2005 08:29:04.0251 (UTC) FILETIME=[9D33D4B0:01C5FC9A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Content-Transfer-Encoding: 7bit
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>, <mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>, <mailto:monami6-request@ietf.org?subject=subscribe>
Sender: monami6-bounces@ietf.org
Errors-To: monami6-bounces@ietf.org
Hi! Ryuji Wakikawa wrote: > > > At Fri, 02 Dec 2005 09:38:57 +0800, > Benjamin Koh wrote: >> Hi! >> >> Replies inline. >> >>> > I am concerned about the issue which is described in 6.2.3 >>> > (Simultaneous location in home and foreign networks) of >>> > draft-montavont-mobileip-multihoming-pb-statement-05.txt. >>> > In order to achieve the goals of Monami6. even if when a MN is >>> > connected to both Home and Foreign networks, I think that a >>> > HA should be >>> > able to be aware of the existence of multiple paths to the >>> > MN including >>> > the path to the MN's interface connected to the home network because >>> > this is necessity for allowing the HA to initiate a change of >>> > forwarding destination. >>> > >>> > With regard to this issue, one available method is that a MN creates >>> > CoA(home CoA) at a home network and assigns it to the interface >>> > connected to the home network so that it can register it as new >>> > forwarding destination in addition to other forwarding destinations >>> > for the interfaces connected to a foreign network and also a HA can >>> > maintain multiple paths to the MN. >>> > Any thoughts on this? >>> >>> => I think it's an important issue and will definitely address it >>> in the final solution. However, I don't think we can/need to create a >>> "home CoA". We might be able to get away with specifying in the signalling >>> that only the flows explicitly specified should be forwarded to the >>> CoA, otherwise, they should be forwarded using normal routing. >> [BK] >> >From what I understand in the MCoA draft, when the primary interface >> returns home, all bindings are deleted. In that case how does the HA >> know to forward the traffic to a CoA rather than simply assume that the >> MN is at home (or can the HA even receive the incoming traffic assuming >> that it is >> not the default home router)? > > There are two options in the current draft. See Appendix-B. > One is when MN returns home with primary interface. MN deletes all > bindings. Second is when MN returns with non-primary IF. MN will > delete binding for the non-primary IF (if it's active on HA) and keeps > other binding. So the choice is between only using home link (home with primary interface) and only using foreign link (returns with non-primary IF). In both cases I'm still not utilising my multiple links to their fullest potential. > Note that, if RO is used, MN can utilize multiple paths even if it is > at home. I believe that's only if CN is mobility-aware, if CN is a normal IPv6 node I don't think RO can be used. Regards, Ben > regards, > ryuji > >> Regards, >> Ben >> >>> Hesham >>> >>> >>> >>> > >>> > Regards, >>> > Keigo >>> > >>> > >>> > >>> > _______________________________________________ >>> > Monami6 mailing list >>> > Monami6@ietf.org >>> > https://www1.ietf.org/mailman/listinfo/monami6 >>> > >>> >>> =========================================================== >>> This email may contain confidential and privileged material for the sole use >>> of the intended recipient. Any review or distribution by others is strictly >>> prohibited. If you are not the intended recipient please contact the sender >>> and delete all copies. >>> =========================================================== >>> >>> >>> _______________________________________________ >>> Monami6 mailing list >>> Monami6@ietf.org >>> https://www1.ietf.org/mailman/listinfo/monami6 >>> >> _______________________________________________ >> Monami6 mailing list >> Monami6@ietf.org >> https://www1.ietf.org/mailman/listinfo/monami6 >> > _______________________________________________ Monami6 mailing list Monami6@ietf.org https://www1.ietf.org/mailman/listinfo/monami6
- [Monami6] Simultaneous location in home and forei… Keigo Aso
- RE: [Monami6] Simultaneous location in home and f… Soliman, Hesham
- Re: [Monami6] Simultaneous location in home and f… Benjamin Koh
- Re: [Monami6] Simultaneous location in home and f… Benjamin Koh
- Re: [Monami6] Simultaneous location in home and f… Vidya Narayanan
- Re: [Monami6] Simultaneous location in home and f… Keigo Aso
- Re: [Monami6] Simultaneous location in home and f… Vidya Narayanan
- Re: [Monami6] Simultaneous location in home and f… Keigo Aso
- Re: [Monami6] Simultaneous location in home and f… Ryuji Wakikawa
- Re: [Monami6] Simultaneous location in home and f… Ryuji Wakikawa
- Re: [Monami6] Simultaneous location in home and f… Benjamin Koh
- Re: [Monami6] Simultaneous location in home and f… Chan-Wah NG
- RE: [Monami6] Simultaneous location in home and f… Soliman, Hesham
- RE: [Monami6] Simultaneous location in home and f… Chan-Wah NG
- Re: [Monami6] Simultaneous location in home and f… Ryuji Wakikawa
- Re: [Monami6] Simultaneous location in home and f… Chan-Wah NG
- Re: [Monami6] Simultaneous location in home and f… Chan-Wah NG
- Re: [Monami6] Simultaneous location in home and f… Benjamin Koh
- Re: [Monami6] Simultaneous location in home and f… Keigo Aso
- Re: [Monami6] Simultaneous location in home and f… Keigo Aso