Re: [multipathtcp] I-D Action:draft-ietf-mptcp-architecture-05.txt

"Ford, Alan" <alan.ford@roke.co.uk> Fri, 21 January 2011 16:49 UTC

Return-Path: <prvs=1002f11ad7=alan.ford@roke.co.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 EEA9E3A6A53 for <multipathtcp@core3.amsl.com>; Fri, 21 Jan 2011 08:49:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.414
X-Spam-Level:
X-Spam-Status: No, score=-3.414 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 mnA6ztQvbcUn for <multipathtcp@core3.amsl.com>; Fri, 21 Jan 2011 08:49:49 -0800 (PST)
Received: from ixe-mta-29.emailfiltering.com (ixe-mta-29-tx.emailfiltering.com [194.116.199.160]) by core3.amsl.com (Postfix) with ESMTP id 0A4A73A6A2B for <multipathtcp@ietf.org>; Fri, 21 Jan 2011 08:49:48 -0800 (PST)
Received: from salt-ext.roke.co.uk ([109.207.29.2]) by ixe-mta-29.emailfiltering.com with emfmta (version 4.8.0.410) vanilla id 264214102 for multipathtcp@ietf.org; 6a85a5d70d1ad5c7; Fri, 21 Jan 2011 16:52:34 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 21 Jan 2011 16:52:26 -0000
Message-ID: <2181C5F19DD0254692452BFF3EAF1D680C091016@rsys005a.comm.ad.roke.co.uk>
In-Reply-To: <20110121164501.29805.80620.idtracker@localhost>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [multipathtcp] I-D Action:draft-ietf-mptcp-architecture-05.txt
Thread-Index: Acu5i0T8Utv54FfIRYi4FHX+LGLvmAAAATKw
References: <20110121164501.29805.80620.idtracker@localhost>
From: "Ford, Alan" <alan.ford@roke.co.uk>
To: multipathtcp@ietf.org
Subject: Re: [multipathtcp] I-D Action:draft-ietf-mptcp-architecture-05.txt
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, 21 Jan 2011 16:49:51 -0000

Hi all,

This new version addresses comments/discusses received from the IESG:

* Break-before-make now introduced in S2.2.1 (Russ/Joel)
* Urgent pointer clarified and toned down (Jari/Cullen)
* Connection ID text rearranged (Alexey)
* MIB comments added (David/Dan)
* ECMP introduced in introduction (Stewart)

Also minor clarity and editorial issues raised by Joel and Juergen all
corrected (notably in intro and S2.2.1).

Many thanks for all the feedback.

Regards,
Alan

> -----Original Message-----
> From: multipathtcp-bounces@ietf.org
[mailto:multipathtcp-bounces@ietf.org] On
> Behalf Of Internet-Drafts@ietf.org
> Sent: 21 January 2011 16:45
> To: i-d-announce@ietf.org
> Cc: multipathtcp@ietf.org
> Subject: [multipathtcp] I-D
Action:draft-ietf-mptcp-architecture-05.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multipath TCP Working Group of the
IETF.
> 
> 
> 	Title           : Architectural Guidelines for Multipath TCP
> Development
> 	Author(s)       : A. Ford, et al.
> 	Filename        : draft-ietf-mptcp-architecture-05.txt
> 	Pages           : 29
> 	Date            : 2011-01-21
> 
> Hosts are often connected by multiple paths, but TCP restricts
> communications to a single path per transport connection.  Resource
> usage within the network would be more efficient were these multiple
> paths able to be used concurrently.  This should enhance user
> experience through improved resilience to network failure and higher
> throughput.
> 
> This document outlines architectural guidelines for the development
> of a Multipath Transport Protocol, with references to how these
> architectural components come together in the development of a
> Multipath TCP protocol.  This document lists certain high level
> design decisions that provide foundations for the design of the MPTCP
> protocol, based upon these architectural requirements.
> 
> A URL for this Internet-Draft is:
>
http://www.ietf.org/internet-drafts/draft-ietf-mptcp-architecture-05.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.