RFC 6182: Architectural Guidelines for Multipath TCP Development

Hosts are often connected by multiple paths, but TCP restricts communications to a single path per transport connection. Resource usage within the network…

Read RFC 6182 on the RFC Editor

Outgoing relationships (14 related RFCs)

Informative reference — RFC 4960: Stream Control Transmission Protocol
Informative reference — RFC 3022: Traditional IP Network Address Translator (Traditional NAT)
Informative reference — RFC 2018: TCP Selective Acknowledgment Options
Informative reference — RFC 3234: Middleboxes: Taxonomy and Issues
Informative reference — RFC 3135: Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations
Informative reference — RFC 4987: TCP SYN Flooding Attacks and Common Mitigations
Informative reference — RFC 5961: Improving TCP's Robustness to Blind In-Window Attacks
Informative reference — RFC 2775: Internet Transparency
Informative reference — RFC 2979: Behavior of and Requirements for Internet Firewalls
Informative reference — RFC 4022: Management Information Base for the Transmission Control Protocol (TCP)
Informative reference — RFC 6181: Threat Analysis for TCP Extensions for Multipath Operation with Multiple Addresses
Informative reference — RFC 2992: Analysis of an Equal-Cost Multi-Path Algorithm
Informative reference — RFC 4898: TCP Extended Statistics MIB
Informative reference — RFC 6093: On the Implementation of the TCP Urgent Mechanism

Incoming relationships (7 related RFCs)

Normatively referenced by — RFC 6824: TCP Extensions for Multipath Operation with Multiple Addresses
Normatively referenced by — RFC 7414: A Roadmap for Transmission Control Protocol (TCP) Specification Documents
Normatively referenced by — RFC 6897: Multipath TCP (MPTCP) Application Interface Considerations
Normatively referenced by — RFC 6629: Considerations on the Application of the Level 3 Multihoming Shim Protocol for IPv6 (Shim6)
Informatively referenced by — RFC 8684: TCP Extensions for Multipath Operation with Multiple Addresses
Informatively referenced by — RFC 7556: Multiple Provisioning Domain Architecture
Informatively referenced by — RFC 8961: Requirements for Time-Based Loss Detection