Re: [Monami6] Simultaneous location in home and foreign

Benjamin Koh <benjamin.kohtm@sg.panasonic.com> Fri, 02 December 2005 02:19 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 1Ei0WV-0004vn-KV; Thu, 01 Dec 2005 21:19:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhzKf-0001Yl-Qd for monami6@megatron.ietf.org; Thu, 01 Dec 2005 20:03:25 -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 UAA13559 for <monami6@ietf.org>; Thu, 1 Dec 2005 20:02:38 -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 1EhzfE-0007Ms-N3 for monami6@ietf.org; Thu, 01 Dec 2005 20:24:42 -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/kings) with ESMTP id jB2139cq028087 for <monami6@ietf.org>; Fri, 2 Dec 2005 10:03:09 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx1) with ESMTP id jB213A022647 for <monami6@ietf.org>; Fri, 2 Dec 2005 10:03:10 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1]) by mail.jp.panasonic.com (8.11.6p2/3.7W/phillies) with ESMTP id jB213AV03781 for <monami6@ietf.org>; Fri, 2 Dec 2005 10:03:10 +0900 (JST)
Received: from [10.81.113.125] ([10.81.113.125]) by pslexc01.psl.local with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Dec 2005 08:59:59 +0800
Message-ID: <438F9D5A.6060809@sg.panasonic.com>
Date: Fri, 02 Dec 2005 09:03: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>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD03274ACD@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Dec 2005 00:59:59.0213 (UTC) FILETIME=[B7D111D0:01C5F6DB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 01 Dec 2005 21:19:42 -0500
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!

Soliman, Hesham wrote:
> 
>  > 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 even receive the incoming traffic assuming the HA is
not the default home router)?

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