Architectural Guidelines for Multipath TCP Development
RFC 6182, “Architectural Guidelines for Multipath TCP Development”, is an Informational document published in March 2011 by A. Ford, C. Raiciu, M. Handley, S. Barre, J. Iyengar. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6182 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6181 Threat Analysis for TCP Extensions for Multipath Operation with Multiple Addresses
- RFC 6183 IP Flow Information Export Mediation: Framework
- RFC 6180 Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment
- RFC 6184 RTP Payload Format for H.264 Video
- RFC 6179 The Internet Routing Overlay Network
- RFC 6185 RTP Payload Format for H.264 Reduced-Complexity Decoding Operation Video
- RFC 6178 Label Edge Router Forwarding of IPv4 Option Packets
- RFC 6186 Use of SRV Records for Locating Email Submission/Access Services