Search RFCs

RFC Editor

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 listmultipathtcp@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 perconnection, yet multiple paths often exist between peers. Thesimultaneous use of these multiple paths for a TCP/IP session wouldimprove resource usage within the network and thus improve userexperience through higher throughput and improved resilience tonetwork failure.

Multipath TCP provides the ability to simultaneously use multiplepaths between peers. This document presents a set of extensions totraditional TCP to support multipath operation. The protocol offersthe same type of service to applications as TCP (i.e., a reliablebytestream), and it provides the components necessary to establishand use multiple TCP flows across potentially disjoint paths.

This document specifies v1 of Multipath TCP, obsoleting v0 asspecified in RFC 6824, through clarifications and modificationsprimarily driven by deployment experience.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.