Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

A. Ford
C. Raiciu
M. Handley
S. Barre
J. Iyengar

Stream:

IETF

Source:

mptcp (tsv)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

Hosts are often connected by multiple paths, but TCP restrictscommunications to a single path per transport connection. Resourceusage within the network would be more efficient were these multiplepaths able to be used concurrently. This should enhance userexperience through improved resilience to network failure and higherthroughput.

This document outlines architectural guidelines for the developmentof a Multipath Transport Protocol, with references to how thesearchitectural components come together in the development of aMultipath TCP (MPTCP). This document lists certain high-level designdecisions that provide foundations for the design of the MPTCPprotocol, based upon these architectural requirements. This document is not an Internet Standards Track specification; it ispublished for informational purposes.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.