[multipathtcp] Last Call: <draft-ietf-mptcp-rfc6824bis-13.txt> (TCP Extensions for Multipath Operation with Multiple Addresses) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 12 April 2019 16:57 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
CC: 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
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <155508825088.16951.6227948364597097521.idtracker@ietfa.amsl.com>
Date: Fri, 12 Apr 2019 09:57:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Y4i7SVTKrqAM39wTQt8nYn7mAvc>
Subject: [multipathtcp] Last Call: <draft-ietf-mptcp-rfc6824bis-13.txt> (TCP Extensions for Multipath Operation with Multiple Addresses) to Proposed Standard

The IESG has received a request from the Multipath TCP WG (mptcp) to consider
the following document: - 'TCP Extensions for Multipath Operation with
Multiple Addresses'
<draft-ietf-mptcp-rfc6824bis-13.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2019-04-26. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract

TCP/IP communication is currently restricted to a single path per
connection, yet multiple paths often exist between peers. The
simultaneous use of these multiple paths for a TCP/IP session would
improve resource usage within the network and, thus, improve user
experience through higher throughput and improved resilience to
network failure.

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.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/ballot/

The following IPR Declarations may be related to this I-D:

https://datatracker.ietf.org/ipr/1842/
https://datatracker.ietf.org/ipr/1843/
https://datatracker.ietf.org/ipr/3242/

The document contains these normative downward references.
See RFC 3967 for additional information:
rfc6182: Architectural Guidelines for Multipath TCP Development (Informational - IETF stream)

[multipathtcp] Last Call: <draft-ietf-mptcp-rfc68… The IESG