TCP Extensions for Multipath Operation with Multiple Addresses

The information below is for an old version of the document
Document Type Expired Internet-Draft (mptcp WG)
Last updated 2017-05-01 (latest revision 2016-10-28)
Replaces draft-bonaventure-mptcp-exp-option
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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


TCP/IP communication is currently restricted to a single path per connection, yet multiple paths often exist between peers. The simultaneous use of these multiple paths for a TCP/IP session would improve resource usage within the network and, thus, improve user experience through higher throughput and improved resilience to network failure. Multipath TCP provides the ability to simultaneously use multiple paths between peers. This document presents a set of extensions to traditional TCP to support multipath operation. The protocol offers the same type of service to applications as TCP (i.e., reliable bytestream), and it provides the components necessary to establish and use multiple TCP flows across potentially disjoint paths. This document specifies v1 of Multipath TCP, obsoleting v0 as specified in RFC6824 [RFC6824] through clarifications and modifications primarily driven by deployment experience.


Alan Ford (
Costin Raiciu (
Mark Handley (
Olivier Bonaventure (
Christoph Paasch (

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