Architectural Guidelines for Multipath TCP Development

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 28
Abstract: Hosts are often connected by multiple paths, but TCP restricts communications to a single path per transport connection. Resource usage within the network would be more efficient were these multiple paths able to be used concurrently. This should enhance user experience through improved resilience to network failure and higher throughput. This document outlines architectural guidelines for the development of a Multipath Transport Protocol, with references to how these architectural components come together in the development of a Multipath TCP (MPTCP). This document lists certain high-level design decisions that provide foundations for the design of the MPTCP protocol, based upon these architectural requirements. This document is not an Internet Standards Track specification; it is published for informational purposes.
Publication Date: 2011-03-01
Status Note: Informational
DOI: 10.17487/RFC6182
Link: https://doi.org/10.17487/RFC6182
Author(s): Alan Ford
Costin Raiciu
Mark J. Handley
Sebastien Barre
Jana Iyengar
Keyword(s): MPTCP

Latest version of IETF RFC 6182

Document Versions — IETF RFC 6182

▶ IETF RFC 6182 (2011-03-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 793 [Superseded*]
IETF RFC 2119 [Active*]

Bibliographic Reference(s)

Handley, M., Paxson, V., and C. Kreibich, "Network Intrusion Detection: Evasion, Traffic Normalization, and End-to-End Protocol Semantics", Usenix Security 2001, 2001, < http:// www.usenix.org/events/sec01/full_papers/handley/handley.pdf >. EXTERNAL
Raiciu, C., Handley, M., and D. Wischik, "Coupled Congestion Control for Multipath Transport Protocols", Work in Progress, March 2011. EXTERNAL
Ford, A., Raiciu, C., Handley, M., and O. Bonaventure, "TCP Extensions for Multipath Operation with Multiple Addresses", Work in Progress, March 2011. EXTERNAL
Ford, B. and J. Iyengar, "Breaking Up the Transport Logjam", ACM HotNets, October 2008. EXTERNAL
Becke, M., Dreibholz, T., Iyengar, J., Natarajan, P., and M. Tuexen, "Load Sharing for the Stream Control Transmission Protocol (SCTP)", Work in Progress, December 2010. EXTERNAL
Wischik, D., Handley, M., and M. Bagnulo Braun, "The Resource Pooling Principle", ACM SIGCOMM CCR vol. 38 num. 5, pp. 47-52, October 2008, < http://ccr.sigcomm.org/online/files/p47-handleyA4.pdf >. EXTERNAL
Scharf, M. and A. Ford, "MPTCP Application Interface Considerations", Work in Progress, March 2011. EXTERNAL
IETF RFC 2018 [Active*]
IETF RFC 2775 [Active*]
IETF RFC 2979 [Active*]
IETF RFC 2992 [Active*]
IETF RFC 3022 [Active*]
IETF RFC 3135 [Active*]
IETF RFC 3234 [Active*]
IETF RFC 4022 [Active*]
IETF RFC 4898 [Active*]
IETF RFC 4960 [Superseded*]
IETF RFC 4987 [Active*]
IETF RFC 5961 [Active*]
IETF RFC 6093 [Superseded*]
IETF RFC 6181 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC6182.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 6182, Architectural Guidelines for Multipath TCP Development. Available at https://doi.org/10.17487/RFC6182

Snippet:

IETF RFC 6182, Architectural Guidelines for Multipath TCP Development. Available at https://doi.org/10.17487/RFC6182

HTML (ISO 690 compliant)

Preview:

IETF RFC 6182, Architectural Guidelines for Multipath TCP Development. Available at https://doi.org/10.17487/RFC6182

Snippet:

<span class="citation"><cite>IETF RFC 6182</cite>, Architectural Guidelines for Multipath TCP Development. Available at <a href="https://doi.org/10.17487/RFC6182" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6182</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 6182, Architectural Guidelines for Multipath TCP Development
doi: 10.17487/RFC6182
url: https://doi.org/10.17487/RFC6182

Snippet:

<li>
<cite id="bib-rfc6182">IETF RFC 6182</cite>, Architectural Guidelines for Multipath TCP Development
<span class="doi">10.17487/RFC6182</span>
</li>

Referenced By

IETF RFC 6418 [Active*]
IETF RFC 6824 [Superseded*]
IETF RFC 6897 [Active*]
IETF RFC 7414 [Active*]