Architectural Guidelines for Multipath TCP Development
draft-ford-mptcp-architecture-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alan Ford , Costin Raiciu , Sebastien Barre , Jana Iyengar , Bryan Ford | ||
| Last updated | 2010-05-21 (Latest revision 2010-02-03) | ||
| Replaced by | draft-ietf-mptcp-architecture | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-mptcp-architecture | |
| 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
Often endpoints are connected by multiple paths, but the nature of TCP/IP restricts communications to a single path per socket. 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 Multipath TCP (MPTCP) protocol. This document also lists certain high level design decisions that provide foundations for the MPTCP design, based upon these architectural requirements.
Authors
Alan Ford
Costin Raiciu
Sebastien Barre
Jana Iyengar
Bryan Ford
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)