IETF Logo Mail Archive

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

Erik Nordmark <Erik.Nordmark@sun.com> Thu, 13 November 2003 22:36 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25175 for <mip4-archive@odin.ietf.org>; Thu, 13 Nov 2003 17:36:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKQ4K-0004bu-T1 for mip4-archive@odin.ietf.org; Thu, 13 Nov 2003 17:36:08 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hADMa4xq017558 for mip4-archive@odin.ietf.org; Thu, 13 Nov 2003 17:36:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKQ4J-0004Wp-PB for mip4-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 17:36:03 -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 RAA25137 for <mip4-web-archive@ietf.org>; Thu, 13 Nov 2003 17:35:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKQ4H-0006tp-00 for mip4-web-archive@ietf.org; Thu, 13 Nov 2003 17:36:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKQ4G-0006tm-00 for mip4-web-archive@ietf.org; Thu, 13 Nov 2003 17:36:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKQ4I-0004UT-72; Thu, 13 Nov 2003 17:36:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKQ3o-0004Nu-Jw for mip4@optimus.ietf.org; Thu, 13 Nov 2003 17:35:32 -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 RAA25048; Thu, 13 Nov 2003 17:35:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKQ3l-0006tE-00; Thu, 13 Nov 2003 17:35:29 -0500
Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx with esmtp (Exim 4.12) id 1AKQ3l-0006tB-00; Thu, 13 Nov 2003 17:35:29 -0500
Received: from bebop.France.Sun.COM ([129.157.174.15]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id hADMZO5u025263; Thu, 13 Nov 2003 15:35:25 -0700 (MST)
Received: from lillen (punchin-nordmark.Eng.Sun.COM [192.9.61.11]) by bebop.France.Sun.COM (8.11.7p1+Sun/8.10.2/ENSMAIL,v2.2) with SMTP id hADMZKQ08048; Thu, 13 Nov 2003 23:35:20 +0100 (MET)
Date: Thu, 13 Nov 2003 23:34:21 +0100
From: Erik Nordmark <Erik.Nordmark@sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@sun.com>
To: James Kempf <kempf@docomolabs-usa.com>
Cc: nemo@ietf.org, mip4@ietf.org, mip6@ietf.org, mipshop@ietf.org
In-Reply-To: "Your message with ID" <00f601c3a97d$991aea70$85818182@dclkempt40>
Message-ID: <Roam.SIMC.2.0.6.1068762861.21338.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET="US-ASCII"
Subject: [Mip4] 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>

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.

  Erik


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

v2.23.0 | Report a Bug | By Email