Document Action: 'Architectural Guidelines for Multipath TCP Development' to Informational RFC (draft-ietf-mptcp-architecture-05.txt)

The IESG <> Wed, 26 January 2011 16:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5142D3A67EF; Wed, 26 Jan 2011 08:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3cicQPDeT4DF; Wed, 26 Jan 2011 08:41:56 -0800 (PST)
Received: from [] (localhost []) by (Postfix) with ESMTP id A08F03A6889; Wed, 26 Jan 2011 08:41:55 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'Architectural Guidelines for Multipath TCP Development' to Informational RFC (draft-ietf-mptcp-architecture-05.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110126164155.24095.36228.idtracker@localhost>
Date: Wed, 26 Jan 2011 08:41:55 -0800
Cc: mptcp mailing list <>, mptcp chair <>, Internet Architecture Board <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 26 Jan 2011 16:41:57 -0000

The IESG has approved the following document:
- 'Architectural Guidelines for Multipath TCP Development'
  (draft-ietf-mptcp-architecture-05.txt) as an Informational RFC

This document is the product of the Multipath TCP Working Group.

The IESG contact person is Lars Eggert.

A URL of this Internet Draft is:

Technical Summary

  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.

Working Group Summary

  This is a product of the MPTCP WG. There is a consensus in
  the WG for publication as an informational RFC. 

  There is a very solid WG
  consensus behind the document. It captures the key high-level design decisions
  about the MPTCP protocol, which have been reached after extensive discussion and
  agreement at the IETF meetings and on the list.

Document Quality

  There is already an implementation of the protocol (draft-ietf-
  mptcp-multiaddressed) that implements the architecture and high-level design
  decisions in this document, 

  There were five detailed reviews of versions of the document. No substantial
  issues were raised. Expert reviews (MIB doctor etc) were not applicable.


  Philip Eardley ( is the Document Shepherd.
  Lars Eggert ( reviewed the document for the IESG.