[tsvwg] RFC 9897 on Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple Addresses
rfc-editor@rfc-editor.org Thu, 08 January 2026 00:47 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 653DFA47A61B; Wed, 7 Jan 2026 16:47:51 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 2DE69C000CC0; Wed, 7 Jan 2026 16:47:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260108004751.2DE69C000CC0@rfcpa.rfc-editor.org>
Date: Wed, 07 Jan 2026 16:47:51 -0800
Message-ID-Hash: PUFMG7NMQYWD25ZJFAE47K3QG5ISJ7JR
X-Message-ID-Hash: PUFMG7NMQYWD25ZJFAE47K3QG5ISJ7JR
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tsvwg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tsvwg@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tsvwg] RFC 9897 on Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple Addresses
List-Id: Transport Area Working Group <tsvwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/S5TIp32wwHqY5SaYxFB0_mkaLZ8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Owner: <mailto:tsvwg-owner@ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Subscribe: <mailto:tsvwg-join@ietf.org>
List-Unsubscribe: <mailto:tsvwg-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9897
Title: Datagram Congestion Control Protocol (DCCP)
Extensions for Multipath Operation with Multiple
Addresses
Author: M. Amend, Ed.,
A. Brunstrom,
A. Kassler,
V. Rakocevic,
S. Johnson
Status: Standards Track
Stream: IETF
Date: January 2026
Mailbox: markus.amend@telekom.de,
anna.brunstrom@kau.se,
andreas.kassler@kau.se,
veselin.rakocevic.1@city.ac.uk,
stephen.h.johnson@bt.com
Pages: 46
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tsvwg-multipath-dccp-24.txt
URL: https://www.rfc-editor.org/info/rfc9897
DOI: 10.17487/RFC9897
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.
This document is a product of the Transport and Services Working Group Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team