Skip to main content

MPTCP Application Interface Considerations

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Michael Scharf , Alan Ford
Last updated 2011-01-12 (Latest revision 2010-11-22)
Replaced by draft-ietf-mptcp-api
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mptcp-api
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:


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.


Michael Scharf
Alan Ford

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