Multi-Connection TCP (MCTCP) Transport
draft-scharf-mptcp-mctcp-01

Document Type Expired Internet-Draft (individual)
Last updated 2010-07-12
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized 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-scharf-mptcp-mctcp-01.txt

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

Michael Scharf (michael.scharf@alcatel-lucent.com)

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