[multipathtcp] MPTCP Architecture Draft available

"Ford, Alan" <alan.ford@roke.co.uk> Mon, 19 October 2009 18:34 UTC

Return-Path: <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 1F63028C0E2 for <multipathtcp@core3.amsl.com>; Mon, 19 Oct 2009 11:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.185
X-Spam-Level:
X-Spam-Status: No, score=-1.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 PdVIxNdlQutp for <multipathtcp@core3.amsl.com>; Mon, 19 Oct 2009 11:34:48 -0700 (PDT)
Received: from rsys001x.roke.co.uk (rsys001x.roke.co.uk [193.118.201.108]) by core3.amsl.com (Postfix) with ESMTP id 52FCD28C142 for <multipathtcp@ietf.org>; Mon, 19 Oct 2009 11:32:44 -0700 (PDT)
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85]) by rsys001x.roke.co.uk (8.13.1/8.13.1) with ESMTP id n9JIWf5Y009139 for <multipathtcp@ietf.org>; Mon, 19 Oct 2009 19:32:41 +0100
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: Mon, 19 Oct 2009 19:32:39 +0100
Message-ID: <2181C5F19DD0254692452BFF3EAF1D6808A4526B@rsys005a.comm.ad.roke.co.uk>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: MPTCP Architecture Draft available
Thread-Index: AcpQ6olhuFoW1IUQR3av64cKIRlM5Q==
From: "Ford, Alan" <alan.ford@roke.co.uk>
To: multipathtcp@ietf.org
X-roke-co-uk-MailScanner: Found to be clean
X-roke-co-uk-MailScanner-SpamCheck:
X-roke-co-uk-MailScanner-From: alan.ford@roke.co.uk
Subject: [multipathtcp] MPTCP Architecture Draft available
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, 19 Oct 2009 18:34:49 -0000

Hi all,

We have started work on the beginnings of an Multipath TCP architecture
draft, combining some of the implementation separation that featured in
the -01 of the mptcp/multiaddressed draft with some architectural
considerations from Tng.

http://www.ietf.org/id/draft-ford-mptcp-architecture-00.txt

Comments welcome - but please remember this is very early days!

Cheers,
Alan