MPTCP Application Interface Considerations
draft-scharf-mptcp-api-04

Document Type Replaced Internet-Draft (individual)
Authors Michael Scharf  , Alan Ford 
Last updated 2011-01-12 (latest revision 2010-11-22)
Replaced by RFC 6897
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mptcp-api
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-api-04.txt

Abstract

Multipath TCP (MPTCP) adds the capability of using multiple paths to a regular TCP session. Even though it is designed to be totally backward compatible to applications, the data transport differs compared to regular TCP, and there are several additional degrees of freedom that applications may wish to exploit. This document summarizes the impact that MPTCP may have on applications, such as changes in performance. Furthermore, it discusses compatibility issues of MPTCP in combination with non-MPTCP-aware applications. Finally, the document describes a basic application interface for MPTCP-aware applications that provides access to multipath address information and a level of control equivalent to regular TCP.

Authors

Michael Scharf (michael.scharf@alcatel-lucent.com)
Alan Ford (alanford@cisco.com)

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