Re: [multipathtcp] FW: New Version Notification for draft-ford-mptcp-multiaddressed-02
Rémi Després <remi.despres@free.fr> Fri, 06 November 2009 14:51 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 7C2443A69BE for <multipathtcp@core3.amsl.com>; Fri, 6 Nov 2009 06:51:10 -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 os+mOeRGDdTk for <multipathtcp@core3.amsl.com>; Fri, 6 Nov 2009 06:51:09 -0800 (PST)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 810243A67D6 for <multipathtcp@ietf.org>; Fri, 6 Nov 2009 06:51:07 -0800 (PST)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 6CCEFE080E2; Fri, 6 Nov 2009 15:51:26 +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 3E726E08130; Fri, 6 Nov 2009 15:51:24 +0100 (CET)
In-Reply-To: <2181C5F19DD0254692452BFF3EAF1D6808C85816@rsys005a.comm.ad.roke.co.uk>
References: <2181C5F19DD0254692452BFF3EAF1D6808B826E2@rsys005a.comm.ad.roke.co.uk> <4AF38B0F.4070106@gmail.com> <2181C5F19DD0254692452BFF3EAF1D6808C85816@rsys005a.comm.ad.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset="ISO-8859-1"; delsp="yes"; format="flowed"
Message-Id: <464ADE7C-BE52-48DA-94DC-B1BA38099963@free.fr>
Content-Transfer-Encoding: quoted-printable
From: Rémi Després <remi.despres@free.fr>
Date: Fri, 06 Nov 2009 15:51:15 +0100
To: "Ford, Alan" <alan.ford@roke.co.uk>
X-Mailer: Apple Mail (2.753.1)
Cc: multipathtcp@ietf.org, Scott Brim <scott.brim@gmail.com>
Subject: Re: [multipathtcp] FW: New Version Notification for draft-ford-mptcp-multiaddressed-02
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: Fri, 06 Nov 2009 14:51:10 -0000
Le 6 nov. 09 à 15:34, Ford, Alan a écrit : >> Ford, Alan allegedly wrote on 10/27/2009 10:03 AM: >>> o Do we want a connection identifier in every packet? E.g. >>> would make implementation of IDS much easier? >> >> I think so. What are the arguments against it? It deterministically >> avoids the kind of cases that Joe was concerned about. > > Well the key argument against it would be the overhead it would > create, > and also any issues with option space limits. To deal with the option space limit, a possible approach, which I personally recommend, consists in using a TCP option only in the initial SYN ACK exchange. Once it is established that both ends support MPTCP, a MPTCP service field in in the TCP payload can be used. RD
- [multipathtcp] FW: New Version Notification for d… Ford, Alan
- Re: [multipathtcp] FW: New Version Notification f… John Leslie
- Re: [multipathtcp] FW: New Version Notification f… Scott Brim
- Re: [multipathtcp] FW: New Version Notification f… Scott Brim
- Re: [multipathtcp] FW: New Version Notification f… John Leslie
- Re: [multipathtcp] FW: New Version Notification f… Ford, Alan
- Re: [multipathtcp] FW: New Version Notification f… Rémi Després