RFC 6824: TCP Extensions for Multipath Operation with Multiple Addresses
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8684.
Current version: RFC 8684 — TCP Extensions for Multipath Operation with Multiple Addresses
In plain English — editorial summary, not part of the RFC
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 defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6824
- Published
- January 2013
- Authors
- A. Ford; C. Raiciu; M. Handley; O. Bonaventure
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 64
- Also known as
- —
- Obsoleted by:
- RFC 8684
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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
- RFC 6801Pseudo Content Delivery Protocol (CDP) for Protecting Multiple Source Flows in the Forward Error Correction (FEC) FrameworkCurrent
November 2012
- RFC 6789Congestion Exposure (ConEx) Concepts and Use CasesCurrent
December 2012
- RFC 6865Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAMECurrent
February 2013
- RFC 6773DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT TraversalCurrent
November 2012
- RFC 6888Common Requirements for Carrier-Grade NATs (CGNs)Current
April 2013
- RFC 6889Analysis of Stateful 64 TranslationCurrent
April 2013
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?