[multipathtcp] WG Last call: draft-ietf-mptcp-architecture-02.txt
<philip.eardley@bt.com> Thu, 21 October 2010 13:31 UTC
Return-Path: <philip.eardley@bt.com>
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 B60143A67B1 for <multipathtcp@core3.amsl.com>; Thu, 21 Oct 2010 06:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.608
X-Spam-Level:
X-Spam-Status: No, score=-101.608 tagged_above=-999 required=5 tests=[AWL=0.438, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
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 t5RE+e1I-oYE for <multipathtcp@core3.amsl.com>; Thu, 21 Oct 2010 06:31:26 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.COM [62.239.224.235]) by core3.amsl.com (Postfix) with ESMTP id 1CCA33A68F5 for <multipathtcp@ietf.org>; Thu, 21 Oct 2010 06:31:26 -0700 (PDT)
Received: from EVMHT64-UKRD.domain1.systemhost.net (10.36.3.101) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 21 Oct 2010 14:32:57 +0100
Received: from EMV67-UKRD.domain1.systemhost.net ([169.254.2.194]) by EVMHT64-UKRD.domain1.systemhost.net ([10.36.3.101]) with mapi; Thu, 21 Oct 2010 14:33:00 +0100
From: philip.eardley@bt.com
To: multipathtcp@ietf.org
Date: Thu, 21 Oct 2010 14:33:32 +0100
Thread-Topic: WG Last call: draft-ietf-mptcp-architecture-02.txt
Thread-Index: ActxJHq3ozsGa0esQc24p5sXd7KzAg==
Message-ID: <1287668012.16798.29.camel@Nokia-N900-51-1>
Accept-Language: en-US, en-GB
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [multipathtcp] WG Last call: draft-ietf-mptcp-architecture-02.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: philip.eardley@bt.com
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: Thu, 21 Oct 2010 13:31:27 -0000
We start a WG last call on the architecture draft. Since it's the ietf season, we'll run for longer than usual - until 19th nov. But please try and raise main comments before the ietf or during the wg meeting, so issues can be discussed face to face thanks phil and yoshifumi. ----- Original message ----- > Hi all, > > This new version of the MPTCP Architecture draft should have handled the > review comments received since the last IETF, and should be more > accessible to readers now. Many thanks to Olivier, Gorry, Iljitsch, and > Phil for the reviews. > > Regards, > Alan > > > -----Original Message----- > > From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org> > [mailto:multipathtcp-bounces@ietf.org] On > > Behalf Of Internet-Drafts@ietf.org<mailto:Internet-Drafts@ietf.org> > > Sent: 19 October 2010 08:45 > > To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org> > > Cc: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org> > > Subject: [multipathtcp] I-D > Action:draft-ietf-mptcp-architecture-02.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-02.txt > > Pages : 25 > > Date : 2010-10-19 > > > > 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-02.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. > _______________________________________________ > multipathtcp mailing list > multipathtcp@ietf.org<mailto:multipathtcp@ietf.org> > https://www.ietf.org/mailman/listinfo/multipathtcp >
- [multipathtcp] WG Last call: draft-ietf-mptcp-arc… philip.eardley
- [multipathtcp] REMINDER: WG Last call: draft-ietf… philip.eardley
- Re: [multipathtcp] REMINDER: WG Last call: draft-… philip.eardley