Multipath TCP Support for Single-homed End-systems
draft-wr-mptcp-single-homed-07

Document Type Expired Internet-Draft (individual)
Last updated 2016-09-22 (latest revision 2016-03-21)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-wr-mptcp-single-homed-07.txt

Abstract

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.

Authors

Rolf Winter (rolf.winter@neclab.eu)
Michael Faath (michael.faath@hs-augsburg.de)
Andreas Ripke (andreas.ripke@neclab.eu)

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