RFC 7430: Analysis of Residual Threats and Possible Fixes for Multipath TCP (MPTCP)
In plain English — editorial summary, not part of the RFC
This document analyzes the residual threats for Multipath TCP (MPTCP) and explores possible solutions to address them.
Document record
- Document ID
- RFC7430
- Published
- July 2015
- Authors
- M. Bagnulo; C. Paasch; F. Gont; O. Bonaventure; C. Raiciu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6181Threat Analysis for TCP Extensions for Multipath Operation with Multiple AddressesCurrent
March 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
- RFC 2747RSVP Cryptographic AuthenticationUpdated
January 2000
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?