RFC 9897: Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple Addresses
In plain English — editorial summary, not part of the RFC
Datagram Congestion Control Protocol (DCCP) communications, as defined in RFC 4340, are inherently restricted to a single path per connection, despite the availability of multiple network paths between peers. The ability to utilize multiple paths simultaneously for a DCCP session can enhance network resource utilization, improve throughput, and increase resilience to network failures, ultimately enhancing the user experience. Use cases for Multipath DCCP (MP-DCCP) include mobile devices (e.g., handsets and vehicles) and residential home gateways that maintain simultaneous connections to distinct network types such as cellular and Wireless Local Area Networks (WLANs) or cellular and fixed access networks. Compared to existing multipath transport protocols, such as Multipath TCP (MPTCP), MP-DCCP is particularly suited for latency-sensitive applications with varying requirements for reliability and in-order delivery. This document specifies a set of protocol extensions to DCCP that enable multipath operations. These extensions maintain the same service model as DCCP while introducing mechanisms to establish and utilize multiple concurrent DCCP flows across different network paths.
Document record
- Document ID
- RFC9897
- Published
- January 2026
- Authors
- M. Amend; A. Brunstrom; A. Kassler; V. Rakocevic; S. Johnson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 46
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8684TCP Extensions for Multipath Operation with Multiple AddressesCurrent
March 2020
- RFC 9000QUIC: A UDP-Based Multiplexed and Secure TransportCurrent
May 2021
- RFC 7829SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission ProtocolCurrent
April 2016
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 9748Updating the NTP RegistriesCurrent
February 2025
- RFC 9657Time-Variant Routing (TVR) Use CasesCurrent
October 2024
- RFC 9135Integrated Routing and Bridging in Ethernet VPN (EVPN)Current
October 2021
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?