IETF Logo Mail Archive

Re: [multipathtcp] Comments on draft-ietf-mptcp-architecture-02

<L.Wood@surrey.ac.uk> Mon, 29 November 2010 17:32 UTC

Return-Path: <L.Wood@surrey.ac.uk>
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 38A8C28C18B for <multipathtcp@core3.amsl.com>; Mon, 29 Nov 2010 09:32:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 sUYeOO1dR20N for <multipathtcp@core3.amsl.com>; Mon, 29 Nov 2010 09:32:08 -0800 (PST)
Received: from mail72.messagelabs.com (mail72.messagelabs.com [193.109.255.147]) by core3.amsl.com (Postfix) with ESMTP id 1904028C18A for <multipathtcp@ietf.org>; Mon, 29 Nov 2010 09:32:07 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: L.Wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-72.messagelabs.com!1291051997!17698470!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [131.227.200.35]
Received: (qmail 12583 invoked from network); 29 Nov 2010 17:33:17 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-2.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 29 Nov 2010 17:33:17 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.245]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Mon, 29 Nov 2010 17:33:17 +0000
From: L.Wood@surrey.ac.uk
To: alan.ford@roke.co.uk, Michael.Scharf@alcatel-lucent.com, multipathtcp@ietf.org
Date: Mon, 29 Nov 2010 17:33:14 +0000
Thread-Topic: [multipathtcp] Comments on draft-ietf-mptcp-architecture-02
Thread-Index: AcuEwLvFmVUj0qGgTMak2Uouxnh0PALKJ0NAAABrp6A=
Message-ID: <FD7B10366AE3794AB1EC5DE97A93A37316BF4494FD@EXMB01CMS.surrey.ac.uk>
References: <133D9897FB9C5E4E9DF2779DC91E947C045EEB65@SLFSNX.rcs.alcatel-research.de> <2181C5F19DD0254692452BFF3EAF1D680BAABECF@rsys005a.comm.ad.roke.co.uk>
In-Reply-To: <2181C5F19DD0254692452BFF3EAF1D680BAABECF@rsys005a.comm.ad.roke.co.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [multipathtcp] Comments on draft-ietf-mptcp-architecture-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: Mon, 29 Nov 2010 17:32:09 -0000

> SCTP is, however, a completely new transport protocol and
> as such does not meet the network and application compatibility goals as
> specified above.

SCTP went standards-track ten years ago.

completely new, you say?

v2.23.0 | Report a Bug | By Email