{"draft":"draft-ietf-tsvwg-multipath-dccp-24","doc_id":"RFC9897","title":"Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple Addresses","authors":["M. Amend, Ed.","A. Brunstrom","A. Kassler","V. Rakocevic","S. Johnson"],"format":["HTML","TEXT","PDF","XML"],"page_count":"46","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Transport and Services Working Group","abstract":"Datagram Congestion Control Protocol (DCCP) communications, as\r\ndefined in RFC 4340, are inherently restricted to a single path per\r\nconnection, despite the availability of multiple network paths\r\nbetween peers. The ability to utilize multiple paths simultaneously\r\nfor a DCCP session can enhance network resource utilization, improve\r\nthroughput, and increase resilience to network failures, ultimately\r\nenhancing the user experience.\r\n\r\nUse cases for Multipath DCCP (MP-DCCP) include mobile devices (e.g.,\r\nhandsets and vehicles) and residential home gateways that maintain\r\nsimultaneous connections to distinct network types such as cellular\r\nand Wireless Local Area Networks (WLANs) or cellular and fixed access\r\nnetworks. Compared to existing multipath transport protocols, such as\r\nMultipath TCP (MPTCP), MP-DCCP is particularly suited for\r\nlatency-sensitive applications with varying requirements for\r\nreliability and in-order delivery.\r\n\r\nThis document specifies a set of protocol extensions to DCCP that\r\nenable multipath operations. These extensions maintain the same\r\nservice model as DCCP while introducing mechanisms to establish and\r\nutilize multiple concurrent DCCP flows across different network\r\npaths.","pub_date":"January 2026","keywords":["dccp","extensions","multipath","multihomed","subflow","concurrent","simultaneous","mobility","mpdccp","mp-dccp"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC9897","errata_url":null}