I have no objection per se, but I think it would be nice to see some
discussion of alternatives to the problem of adapting QUIC to work over
a reliable and bidirectional transport (as he shamelessly plugs
https://datatracker.ietf.org/doc/draft-gage-quic-qort/ ;-).
/bill
On 2025-12-02 8:21 p.m., Lucas Pardue wrote:
Hi folks,
With chair hat on:
The Datatracker suprised me a bit with the automated email :-)
To add a little more colour to the adoption call, it begins the formal
consensus process for adopting a document as a starting point to
addressing the fourth area of work in our charter.
We saw some strong signals of support for adoption of the draft during
the IETF 124 meeting. There were some people opposed at the time, some
of which appeared to be related to concerns on versioning and
ossification. Since the meeting a draft 01 was published that
incorporates some feedback on these matters.
Please respond on the list to indicate your opinion of adoption of the
draft to the QUIC WG.
Cheers,
Lucas & Matt
QUIC WG Chairs
----- Original message -----
From: Lucas Pardue via Datatracker <[email protected]
<mailto:[email protected]>>
To: [email protected] <mailto:draft-opik-quic-
[email protected]>, [email protected] <mailto:[email protected]>,
[email protected] <mailto:[email protected]>
Subject: Call for adoption: draft-opik-quic-qmux-01 (Ends 2025-12-16)
Date: Wednesday, December 03, 2025 01:03
Subject: Call for adoption: draft-opik-quic-qmux-01 (Ends 2025-12-16)
This message starts a 2-week Call for Adoption for this document.
Abstract:
This document specifies QMux version 1. QMux version 1 provides,
over bi-directional streams such as TLS, the same set of stream and
datagram operations that applications rely upon in QUIC version 1.
Discussion Venues
This note is to be removed before publishing as an RFC.
Discussion of this document takes place on the QUIC Working Group
mailing list ([email protected] <mailto:[email protected]>), which is
archived at
https://mailarchive.ietf.org/arch/browse/quic/ <https://
mailarchive.ietf.org/arch/browse/quic/>.
Source for this draft and an issue tracker can be found at
https://github.com/kazuho/draft-opik-quic-qmux <https://github.com/
kazuho/draft-opik-quic-qmux>.
File can be retrieved from:
https://datatracker.ietf.org/doc/draft-opik-quic-qmux/ <https://
datatracker.ietf.org/doc/draft-opik-quic-qmux/>
Please reply to this message keeping [email protected]
<mailto:[email protected]> in copy by indicating
whether you support or not the adoption of this draft as a WG document.
Comments to motivate your preference are highly appreciated.
Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the
provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].
Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/ <https://
datatracker.ietf.org/doc/bcp78/>
[2] https://datatracker.ietf.org/doc/bcp79/ <https://
datatracker.ietf.org/doc/bcp79/>
[3] https://datatracker.ietf.org/doc/rfc6701/ <https://
datatracker.ietf.org/doc/rfc6701/>
