RFC 6897: Multipath TCP (MPTCP) Application Interface Considerations
In plain English — editorial summary, not part of the RFC
Multipath TCP (MPTCP) adds the capability of using multiple paths to a regular TCP session. Even though it is designed to be totally backward compatible to applications, the data transport differs compared to regular TCP, and there are several additional degrees of freedom that applications may wish to exploit. This document summarizes the impact that MPTCP may have on applications, such as changes in performance. Furthermore, it discusses compatibility issues of MPTCP in combination with non-MPTCP-aware applications. Finally, the document describes a basic application interface that is a simple extension of TCP's interface for MPTCP-aware applications.
Document record
- Document ID
- RFC6897
- Published
- March 2013
- Authors
- M. Scharf; A. Ford
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 31
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6889Analysis of Stateful 64 TranslationCurrent
April 2013
- RFC 6888Common Requirements for Carrier-Grade NATs (CGNs)Current
April 2013
- RFC 6865Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAMECurrent
February 2013
- RFC 6968FCAST: Object Delivery for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) ProtocolsCurrent
July 2013
- RFC 6824TCP Extensions for Multipath Operation with Multiple AddressesObsoleted
January 2013
- RFC 6972Problem Statement and Requirements of the Peer-to-Peer Streaming Protocol (PPSP)Current
July 2013
- RFC 6817Low Extra Delay Background Transport (LEDBAT)Current
December 2012
- RFC 6816Simple Low-Density Parity Check (LDPC) Staircase Forward Error Correction (FEC) Scheme for FECFRAMECurrent
December 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?