datatracker.ietf.org
Sign In
Version 4.51.p2, 2013-06-11
Report a bug

Threat Analysis for TCP Extensions for Multipath Operation with Multiple Addresses
draft-ietf-mptcp-threat-08

RFC
Document Stream: IETF
Last updated: 2011-01-26
Replaces: draft-bagnulo-mptcp-threat
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6181
IANA Action State: No IC 
Responsible AD: Lars Eggert
IESG Note: Yoshifumi Nishida (nishida@sfc.wide.ad.jp) is the document shepherd.
Send notices to: mptcp-chairs@tools.ietf.org, draft-ietf-mptcp-threat@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-threat.

Abstract:
Multipath TCP (MPTCP for short) describes the extensions proposed for TCP so that endpoints of a given TCP connection can use multiple paths to exchange data. 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. 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. This note includes a threat analysis for MPTCP. This document is not an Internet Standards Track specification; it is published for informational purposes.

Authors:
Marcelo Bagnulo <marcelo@it.uc3m.es>

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