RFC 6181: Threat Analysis for TCP Extensions for Multipath Operation with Multiple Addresses
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6181
- Published
- March 2011
- Authors
- M. Bagnulo
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7430Analysis of Residual Threats and Possible Fixes for Multipath TCP (MPTCP)Current
July 2015
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
- RFC 7350Datagram Transport Layer Security (DTLS) as Transport for Session Traversal Utilities for NAT (STUN)Current
August 2014
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
- RFC 3759RObust Header Compression (ROHC): Terminology and Channel Mapping ExamplesCurrent
April 2004
- RFC 3723Securing Block Storage Protocols over IPUpdated
April 2004
- RFC 3097RSVP Cryptographic Authentication -- Updated Message Type ValueCurrent
April 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?