Skip to main content

Multipath TCP Support for Single-homed End-systems

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Rolf Winter , Michael Faath , Andreas Ripke
Last updated 2016-09-22 (Latest revision 2016-03-21)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Multipath TCP relies on the existence of multiple paths between end- systems. These are typically provided by using different IP addresses obtained by different ISPs at the end-systems. While this scenario is certainly becoming increasingly a reality (e.g. mobile devices), currently most end-systems are single-homed (e.g. desktop PCs in an enterprise). It seems also likely that a lot of network sites will insist on having all traffic pass a single network element (e.g. for security reasons) before traffic is split across multiple paths. This memo therefore describes mechanisms to make multiple paths available to multipath TCP-capable end-systems that are not available directly at the end-systems but somewhere within the network.


Rolf Winter
Michael Faath
Andreas Ripke

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)