[multipathtcp] Protocol Action: 'TCP Extensions for Multipath Operation with Multiple Addresses' to Proposed Standard (draft-ietf-mptcp-rfc6824bis-18.txt)

The IESG <iesg-secretary@ietf.org> Mon, 22 July 2019 13:31 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: multipathtcp@ietf.org
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9F3120059; Mon, 22 Jul 2019 06:31:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.99.1
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, mptcp-chairs@ietf.org, multipathtcp@ietf.org, philip.eardley@bt.com, Philip Eardley <philip.eardley@bt.com>, ietf@kuehlewind.net, draft-ietf-mptcp-rfc6824bis@ietf.org, rfc-editor@rfc-editor.org
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <156380228636.28066.4578395807821017833.idtracker@ietfa.amsl.com>
Date: Mon, 22 Jul 2019 06:31:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Dq-7_bV5C6VM4rxmDeh9aTwrmo0>
Subject: [multipathtcp] Protocol Action: 'TCP Extensions for Multipath Operation with Multiple Addresses' to Proposed Standard (draft-ietf-mptcp-rfc6824bis-18.txt)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 22 Jul 2019 13:31:27 -0000

The IESG has approved the following document:
- 'TCP Extensions for Multipath Operation with Multiple Addresses'
  (draft-ietf-mptcp-rfc6824bis-18.txt) as Proposed Standard

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

The IESG contact persons are Mirja K├╝hlewind and Magnus Westerlund.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/





Technical Summary

   Multipath TCP provides the ability to simultaneously use multiple paths between peers.  This document presents a set of extensions to traditional TCP to support multipath operation.  The protocol offers the same type of service to applications as TCP (i.e., reliable bytestream), and it provides the components necessary to establish and use multiple TCP flows across potentially disjoint paths. This document specifies v1 of Multipath TCP, obsoleting v0 as specified in RFC6824, through clarifications and modifications primarily driven by deployment experience. 

Working Group Summary

   After creating the Experimental RFC6824, the primary goal of the MPTCP working group has been to create a bis version of the protocol document on the Standards track, incorporating experience from (for example) implementations, interoperability events, experiments, usage scenarios, protocol corner cases, and feedback from TCPM.	This process led to several changes, a couple of which make RFC6824bis incompatible with RFC6824. Hence this document obsoletes RFC6824.  There is WG agreement to move ahead with publishing the document. 

Document Quality

  This document has been reviewed by various people. There is one (non-public) implementation and other implementers of RFC6824 have indicated that they will implement against the new RFC. The original MPTCP spec has been widely implemented and deployed and the Linux implementation is publicly available. The bis document has been implemented in Linux, but permission to release this code has not been forthcoming. The WG is OK with publishing the RFC at this stage rather than waiting further, and vendors /implementers have indicated that they will implement against the new RFC. 

Personnel

   Philip Eardley is the Document Shepherd and Mirja Kuehlewind is the Responsible Area Director