Threat Analysis for Multi-addressed/Multi-path TCP

Document Type Replaced Internet-Draft (individual)
Author Marcelo Bagnulo 
Last updated 2010-05-21 (latest revision 2010-02-08)
Replaced by RFC 6181
Stream (None)
Intended RFC status (None)
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-threat
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


Multi-addresses/Multi-path TCP (MPTCP for short) describes the extensions proposed for TCP so that each endpoint of a given TCP connection can use multiple IP addresses to exchange data (instead of a single IP address per endpoint as currently defined). Such extensions enable the exchange of segments using different source- destination address pairs, resulting in the capability of using multiple paths in a significant number of scenarios. In particular, some level of multihoming and mobility support can be achieved through these extensions. However, the support for multiple IP addresses per endpoint may have implications on the security of the resulting MPTCP protocol. This note includes a threat analysis for MPTCP.


Marcelo Bagnulo (

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