Multi-Connection TCP (MCTCP) Transport
draft-scharf-mptcp-mctcp-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Michael Scharf | ||
| Last updated | 2010-07-12 | ||
| RFC stream | (None) | ||
| Intended RFC status | (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 transport over potentially different paths can be realized by several coupled Transmission Control Protocol (TCP) connections. Multi-Connection TCP (MCTCP) transport aggregates multiple TCP connections between potentially different addresses into a single session that can be accessed by an application like a single TCP connection. MCTCP encodes control information, as far as possible, in the payload of the TCP connections and therefore requires only minor changes in the TCP implementations, and it is transparent in the single-path case. MCTCP is therefore proposed as a simple, modular, and extensible mechanism for multipath transport.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)