IETF Logo Mail Archive

Re: [multipathtcp] Interesting paper

Rémi Després <remi.despres@free.fr> Wed, 04 November 2009 17:44 UTC

Return-Path: <remi.despres@free.fr>
X-Original-To: multipathtcp@core3.amsl.com
Delivered-To: multipathtcp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BBB83A6832 for <multipathtcp@core3.amsl.com>; Wed, 4 Nov 2009 09:44:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRyv07BXHC1X for <multipathtcp@core3.amsl.com>; Wed, 4 Nov 2009 09:44:37 -0800 (PST)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 4C0403A67E5 for <multipathtcp@ietf.org>; Wed, 4 Nov 2009 09:44:35 -0800 (PST)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 9DCA6E082A0; Wed, 4 Nov 2009 18:44:48 +0100 (CET)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 75455E080DE; Wed, 4 Nov 2009 18:44:45 +0100 (CET)
In-Reply-To: <84a612dd0911031350q669f850by4fd09711daeb6aa8@mail.gmail.com>
References: <EF751D1A-E7F6-425A-AA8D-D41113A8C1B6@gmail.com> <0F5B5ACA-6B54-429B-AE99-03C6D40505C5@cisco.com> <7BB0AC22-A38C-4911-AB39-6A960A90EA1F@cisco.com> <84a612dd0910271707hd2a8564o21e3dae38c2843ad@mail.gmail.com> <20D66F43-AFEE-41D2-AF10-BB06662B0093@cisco.com> <84a612dd0910271756q39ed39c2h9143a0237047d8c7@mail.gmail.com> <9F695526-37CD-4D41-869C-3D59BD9D5913@cisco.com> <80049D27-B7FA-4AF3-A200-2BDEB5AB8E25@cs.ucl.ac.uk> <4AE87562.6010804@it.uc3m.es> <4AF0A372.1030802@isi.edu> <84a612dd0911031350q669f850by4fd09711daeb6aa8@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset="ISO-8859-1"; delsp="yes"; format="flowed"
Message-Id: <BED2D36A-B431-4A89-B647-5B7077968FD6@free.fr>
Content-Transfer-Encoding: quoted-printable
From: Rémi Després <remi.despres@free.fr>
Date: Wed, 04 Nov 2009 18:44:37 +0100
To: Mark Handley <M.Handley@cs.ucl.ac.uk>
X-Mailer: Apple Mail (2.753.1)
Cc: multipathtcp@ietf.org, Bryan Ford <brynosaurus@gmail.com>
Subject: Re: [multipathtcp] Interesting paper
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multipathtcp>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2009 17:44:38 -0000

Le 3 nov. 09 à 22:50, Mark Handley a écrit :

> We definitely intend MP-TCP to work for both v4 and v6.


Sure, as TCP is above IP, MPTCP will naturally work on both.

But isn't the real question whether the protocol will support NAT  
traversals?

If yes, it would be a pity to make the IPv6 solution more complex  
than needed just to support NAT traversals.

Can't we expect that before MPTCP is agreed on and deployed, the vast  
majority of multihomed hosts will have IPv6?

RD

v2.23.0 | Report a Bug | By Email