DCCP Extensions for Multipath Operation with Multiple Addresses

Document Type Expired Internet-Draft (individual)
Last updated 2020-05-07 (latest revision 2019-11-04)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


DCCP communication is currently restricted to a single path per connection, yet multiple paths often exist between peers. The simultaneous use of these 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 failure. Multipath DCCP provides the ability to simultaneously use multiple paths between peers. This document presents a set of extensions to traditional DCCP to support multipath operation. The protocol offers the same type of service to applications as DCCP and it provides the components necessary to establish and use multiple DCCP flows across potentially disjoint paths.


Markus Amend (markus.amend@telekom.de)
Eckard Bogenfeld (eckard.bogenfeld@telekom.de)
Anna Brunstrom (anna.brunstrom@kau.se)
Andreas Kassler (andreas.kassler@kau.se)
Veselin Rakocevic (veselin.rakocevic.1@city.ac.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)