Hi all, as you might have seen we submitted a new version of the QUIC multipath draft after the virtual interop we did last Friday. This draft again as a new transport parameter as there is a small wire-breaking change as we added another field to the PATH_CIDS_BLOCKED frame. So if you are implementing now, please update to the value in -13. There is another chance for interop testing as the upcoming hackathon!
Further there are two small normative changes - We now recommend sending at least one unused CID for all paths up to the max path ID - We changed the error code for MP frames in 0-RTT to align correctly with RFC9000 Then there were some clarifications - around the use, acking, and retransmissions of the PATHS_BLOCKED and PATH_CIDS_BLOCKED, MAX_PATH as well as PATH_AVAILABLE, and - on the use of IV and nonce. Finally, we also updated the example and fixed some smaller editorial nits. That's it. All issues are basically resolved. There is only one open technical issue questioning if PATH_CIDS_BLOCKED is really needed, however, as the client can choose to not implement and the server can mostly choose to ignore it, I believe the default is to keep it, except someone really brings up technical concerns about it. Therefore, the only left item in my view is a larger editorial pass which I will try to do in the coming days. But if everything works out well, I believe we should be ready for WGLC by Bangkok! Mirja On 04.03.25, 02:03, "[email protected] <mailto:[email protected]>" <[email protected] <mailto:[email protected]>> wrote: Internet-Draft draft-ietf-quic-multipath-13.txt is now available. It is a work item of the QUIC (QUIC) WG of the IETF. Title: Multipath Extension for QUIC Authors: 刘彦梅 马云飞 Quentin De Coninck Olivier Bonaventure Christian Huitema Mirja Kuehlewind Name: draft-ietf-quic-multipath-13.txt Pages: 40 Dates: 2025-03-03 Abstract: This document specifies a multipath extension for the QUIC protocol to enable the simultaneous usage of multiple paths for a single connection. 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/quicwg/multipath <https://github.com/quicwg/multipath>. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ <https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/> There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-quic-multipath-13.html <https://www.ietf.org/archive/id/draft-ietf-quic-multipath-13.html> A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-13 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-13> Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts
