Skip to main content

Architectural Guidelines for Multipath TCP Development
RFC 6182

Revision differences

Document history

Date By Action
2023-01-04
Jenny Bui Posted related IPR disclosure Koninklijke KPN N.V.'s Statement about IPR related to RFC 6182 belonging to Nederlandse Organisatie voor Toegepast Natuurwetenschappelijk Onderzoek (TNO)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Hosts are often connected by multiple paths, but TCP restricts communications to a single path per …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-10-14
(System) Notify list changed from mptcp-chairs@ietf.org, draft-ietf-mptcp-architecture@ietf.org to (None)
2011-03-24
Cindy Morgan State changed to RFC Published from RFC Ed Queue.
2011-03-24
Cindy Morgan [Note]: changed to 'RFC 6182'
2011-03-21
(System) RFC published