Skip to main content

TCP Extensions for Multipath Operation with Multiple Addresses

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Alan Ford , Costin Raiciu , Mark J. Handley
Last updated 2010-08-25 (Latest revision 2010-03-09)
Replaced by RFC 6824
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-multiaddressed
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:


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 - reliable bytestream - and provides the components necessary to establish and use multiple TCP flows across potentially disjoint paths.


Alan Ford
Costin Raiciu
Mark J. Handley

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