File formats:

Also available: XML file for editing

 

Status:

PROPOSED STANDARD

Obsoletes:

RFC 6824

Authors:

A. Ford
C. Raiciu
M. Handley
O. Bonaventure
C. Paasch

Stream:

IETF

Source:

mptcp (tsv)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8684

Discuss this RFC: Send questions or comments to the mailing list multipathtcp@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8684

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., a 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 RFC 6824, through clarifications and modifications primarily driven by deployment experience.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.