Multipath TCP Support for Single-homed End-systems
draft-wr-mptcp-single-homed-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Rolf Winter , Andreas Ripke | ||
| Last updated | 2011-06-27 (Latest revision 2011-03-07) | ||
| RFC stream | (None) | ||
| Formats | |||
| 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:
Abstract
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. residential broadband customers). This memo describes mechanisms to make multiple paths available to multipath TCP via autoconfiguration that are not available at the end-systems but somewhere within the network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)