RFC 10069 on Managing Multiple Paths for a QUIC Connection
rfc-editor@rfc-editor.org Sat, 07 November 2026 20:15 UTC
Received: by mx.ietf.org (Postfix) id 5511446; Sat, 07 Nov 2026 20:15:58 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rfc-editor.org; s=mail; t=1794082558; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=MV/U3+nXHjX5Qp5gnQFcvxy5bK+mtnRWyn+zH10d8Pg=; b=JhYrcRbwEnH7jZ4ER6OayHC8z7n9SG9/iOpYTbdMLlZKkXpxMyxQTen11kBibIKONMHi1z zStmgKAmvXTxiXbVmbJO794sw+UXI/4tVp3ihVdt3QkQ1af6fJbCwZqHF/N4HGrtP85VyL RkZJAGNWEkuAnwlLnp/LJofpqtEMGnI=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=rfc-editor@rfc-editor.org
Received: from celery-6bc665db48-75fsm (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 1E9B313BA9007; Sat, 7 Nov 2026 12:15:58 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: RFC 10069 on Managing Multiple Paths for a QUIC Connection
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Sat, 07 Nov 2026 20:15:58 -0000
message-id: <179408255800.14.2206794678807239173@rfc-editor.org>
Message-ID-Hash: 6IJNEH4QITS5XBSLR4DUGP5KUQANWGGE
X-Message-ID-Hash: 6IJNEH4QITS5XBSLR4DUGP5KUQANWGGE
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-quic.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org, quic@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mgPWm0HEM3nRwmRVbUwv8BfWmys>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Owner: <mailto:quic-owner@ietf.org>
List-Post: <mailto:quic@ietf.org>
List-Subscribe: <mailto:quic-join@ietf.org>
List-Unsubscribe: <mailto:quic-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 10069
Title: Managing Multiple Paths for a QUIC Connection
Author: Y. Liu, Ed.,
Y. Ma,
Q. De Coninck, Ed.,
O. Bonaventure,
C. Huitema,
M. Kühlewind, Ed.
Status: Proposed Standard
Stream: IETF
Date: November 2026
Mailbox: miaoji.lym@alibaba-inc.com
yfmascgy@gmail.com,
quentin.deconinck@umons.ac.be,
Olivier.Bonaventure@uclouvain.be,
huitema@huitema.net,
mirja.kuehlewind@ericsson.com
Pages: 33
I-D Tag: draft-ietf-quic-multipath-21
URL: https://www.rfc-editor.org/info/rfc10069
DOI: 10.17487/RFC10069
This document specifies a multipath extension for the QUIC protocol
to enable the simultaneous usage of multiple paths for a single
connection. It introduces explicit path identifiers to create,
delete, and manage multiple paths. This document does not specify
address discovery or management, nor how applications using QUIC
schedule traffic over multiple paths.
This document is a product of the QUIC Working Group of the IETF.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. 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/series/rfc-download/
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