Sign in
Version 5.13.0, 2015-03-25
Report a bug

Multipath TCP Support for Single-homed End-systems

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-01-16 (latest revision 2013-07-15)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


Multipath TCP relies on the existence of multiple paths at the end- systems typically provided through different IP addresses obtained by different ISPs. 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)