The IESG has received a request from the Transport and Services Working Group WG (tsvwg) to consider the following document: - 'DCCP Extensions for Multipath Operation with Multiple Addresses' <draft-ietf-tsvwg-multipath-dccp-17.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the [email protected] mailing lists by 2024-10-17. Exceptionally, comments may be sent to [email protected] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract DCCP communications as defined in RFC 4340 are restricted to a single path per connection, yet multiple paths often exist between peers. The simultaneous use of available multiple paths for a DCCP session could improve resource usage within the network and, thus, improve user experience through higher throughput and improved resilience to network failures. Use cases for Multipath DCCP (MP-DCCP) are mobile devices (e.g., handsets, vehicles) and residential home gateways simultaneously connected to distinct networks as, e.g., a cellular and a Wireless Local Area (WLAN) network or a cellular and a fixed access network. Compared to existing multipath protocols such as MPTCP, MP-DCCP offers special support for latency-sensitive services with different requirements for reliability and in-order delivery. This document specifies a set of extensions to DCCP to support multipath operations. The protocol offers the same type of service to applications as DCCP and provides the components necessary to establish and use multiple DCCP flows across different paths simultaneously. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-tsvwg-multipath-dccp/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/5025/ https://datatracker.ietf.org/ipr/3639/ _______________________________________________ IETF-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]
