[Mip4] Re: [Mip6] Re: [Mipshop] Minutes of Multiple Link Flows BAR BOF

Nicolas Montavont <montavont@clarinet.u-strasbg.fr> Fri, 14 November 2003 03:45 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09699 for <mip4-archive@odin.ietf.org>; Thu, 13 Nov 2003 22:45:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKUtO-0002e9-15 for mip4-archive@odin.ietf.org; Thu, 13 Nov 2003 22:45:06 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE3j5d1010139 for mip4-archive@odin.ietf.org; Thu, 13 Nov 2003 22:45:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKUtN-0002dP-Ha for mip4-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 22:45:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09681 for <mip4-web-archive@ietf.org>; Thu, 13 Nov 2003 22:44:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKUtJ-0004bl-00 for mip4-web-archive@ietf.org; Thu, 13 Nov 2003 22:45:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKUtJ-0004be-00 for mip4-web-archive@ietf.org; Thu, 13 Nov 2003 22:45:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKUtK-0002bn-UX; Thu, 13 Nov 2003 22:45:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKQnd-0008UO-6D for mip4@optimus.ietf.org; Thu, 13 Nov 2003 18:22:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28745 for <mip4@ietf.org>; Thu, 13 Nov 2003 18:22:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKQnZ-0007ki-00 for mip4@ietf.org; Thu, 13 Nov 2003 18:22:49 -0500
Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx with smtp (Exim 4.12) id 1AKQnY-0007kb-00 for mip4@ietf.org; Thu, 13 Nov 2003 18:22:48 -0500
Received: (qmail 30510 invoked for bounce); 13 Nov 2003 23:22:48 -0000
Received: from unknown (HELO clarinet.u-strasbg.fr) (montavont@unknown) by unknown with RC4-MD5 encrypted SMTP; 13 Nov 2003 23:22:48 -0000
Message-ID: <3FB41243.7020502@clarinet.u-strasbg.fr>
Date: Fri, 14 Nov 2003 00:22:43 +0100
From: Nicolas Montavont <montavont@clarinet.u-strasbg.fr>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@sun.com>
CC: James Kempf <kempf@docomolabs-usa.com>, nemo@ietf.org, mip4@ietf.org, mip6@ietf.org, mipshop@ietf.org
References: <Roam.SIMC.2.0.6.1068762861.21338.nordmark@bebop.france>
In-Reply-To: <Roam.SIMC.2.0.6.1068762861.21338.nordmark@bebop.france>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Mip4] Re: [Mip6] Re: [Mipshop] Minutes of Multiple Link Flows BAR BOF
Sender: mip4-admin@ietf.org
Errors-To: mip4-admin@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Erik Nordmark wrote:

>I didn't make it to the bar on Monday due to jetlag.
>
>One observation I have on the desire to send different flows over
>different paths/CoAs.
>
>Looking at possible multihoming solutions (take draft-nordmark-multi6-noid
>as an example one what a solution might look like) the result
>is that the stack would have a mapping from an ID (used by transport protocols)
>to a set of locators for the peer.
>
>This type of example shows that it might be useful to express sending
>different flows over different paths/locators even if mobility isn't used.
>
>Thus I don't think such a scheme, if we are going to define one,
>should be tied to mobility specific signalling.
>
I totally agree with you that if we specify a MIPv6-tied solution for 
"general" multihoming, we may encounter difficulties with non-MNs.
But I think that some points are to be clarified in MIPv6 when the MN is 
multihomed. That is what we are trying to show in 
draft-montavont-pb-statement.

And I'd like to point out another aspect of multihoming, more linked to 
our draft on filtering (draft-montavont-mip6-ha-filtering). Assume that 
you have two interfaces, a WLAN interface and a GPRS interface and you 
currently use the WLAN interface through a reverse tunnel with your home 
agent. Assume that you receive several flows on your pda. One of them is 
a video streaming.

Then you leave the hot spot zone and want to switch your flows on GPRS 
interface. To do so, you send a BU to your HA. In this case, it can be 
very useful to add some filters on what flows you want to be redirected 
and what flows you don't want on your GPRS interface. It seems to me 
that to use the BU in that case is a good solution, because you only 
need to send one message. This does not forbidd the use of other 
mechanisms to manage multihoming in different situations.

Maybe the conclusion of that can be that different problems may lead to 
different solutions. A clear problem statement, from each WG may 
definitly help to clarify the situation.

Nicolas

>
>  Erik
>
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www.ietf.org/mailman/listinfo/mip6
>  
>



-- 
Mip4 mailing list
Mip4@ietf.org
https://www.ietf.org/mailman/listinfo/mip4