datatracker.ietf.org
Sign In
Version 4.45, 2013-05-14
Report a bug

Multipath TCP (MPTCP) Application Interface Considerations
draft-ietf-mptcp-api-07

RFC
Document Stream: IETF
Last updated: 2013-01-19
Replaces: draft-scharf-mptcp-api
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (mptcp)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6897
IANA Action State: No IC 
On agenda of 2012-11-15 IESG telechat
Responsible AD: Martin Stiemerling
Send notices to: mptcp-chairs@tools.ietf.org, draft-ietf-mptcp-api@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-mptcp-api.

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 that is a simple extension of TCP's interface for MPTCP-aware applications.

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)