Hi all, thanks, Yanmei!
Actually, I think there is one more small change that we should mention because it changes the normative requirements slightly: * It is now recommended (SHOULD) to always send the PATH_ABANDON frame on another path than the to-be-abandoned path. Also note that we now have 0 open issues that we need to address! Yeah! So, this is a good time for updating your implementation and we look forward to some more interop testing in the coming weeks! Mirja From: Yanmei Liu <miaoji....@alibaba-inc.com> Reply to: Yanmei Liu <miaoji....@alibaba-inc.com> Date: Wednesday, 22. January 2025 at 14:17 To: quic <quic@ietf.org>, WG Chairs <quic-cha...@ietf.org> Cc: Christian Huitema <huit...@huitema.net>, Mirja Kuehlewind <mirja.kuehlew...@ericsson.com>, "yunfei.ma" <yunfei...@uber.com>, "quentin.deconinck" <quentin.deconi...@umons.ac.be>, "olivier.bonaventure" <olivier.bonavent...@uclouvain.be> Subject: Fw: New Version Notification for draft-ietf-quic-multipath-12.txt Hi Everyone, We submitted a new draft version -12 for multipath extension: https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ The new version contains several modifications: 1. Add PATH_CIDS_BLOCKED frame as an explicit signal for situations when endpoints don’t have unused CIDs for the corresponding path 2. When endpoint sends PATH_ABANDON frame but don’t receive a corresponding PATH_ABANDON, it’s left to the implementation when to release the path resources, but endpoints SHOULD wait at least 3 PTOs before remove the issued CIDs of the path. 3. Packets which only contains PATH_ACK frames are not congestion controlled, but senders should carefully consider the load induced by these packets. 4. Add guidance for handling PTO on multiple paths. 5. It’s recommended to open a new path for active client migration. 6. Update transport parameter for the new version. The diff link between -11 and -12: https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-12<https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-11> Please have a look and feel free to share ideas! Best Regards, Yanmei ------------------------------------------------------------------ From:internet-drafts <internet-dra...@ietf.org> Send Time:2025 Jan. 22 (Wed.) 17:58 To:LIU Yanmei<miaoji....@alibaba-inc.com>; "马云飞"<yunfei...@uber.com>; Christian Huitema<huit...@huitema.net>; Mirja Kuehlewind<mirja.kuehlew...@ericsson.com>; Olivier Bonaventure<olivier.bonavent...@uclouvain.be>; Quentin De Coninck<quentin.deconi...@umons.ac.be>; "quic-chairs"<quic-cha...@ietf.org> Subject:New Version Notification for draft-ietf-quic-multipath-12.txt A new version of Internet-Draft draft-ietf-quic-multipath-12.txt has been successfully submitted by Yanmei Liu and posted to the IETF repository. Name: draft-ietf-quic-multipath Revision: 12 Title: Multipath Extension for QUIC Date: 2025-01-22 Group: quic Pages: 39 URL: https://www.ietf.org/archive/id/draft-ietf-quic-multipath-12.txt Status: https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ HTML: https://www.ietf.org/archive/id/draft-ietf-quic-multipath-12.html HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-quic-multipath Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-12 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 (quic@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/quic/. Source for this draft and an issue tracker can be found at https://github.com/quicwg/multipath. The IETF Secretariat
