Sorry for the mistake, Update the diff link between draft -14 and -15: https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-15
On Wed, 9 Jul 2025 at 11:16, Yanmei Liu <[email protected]> wrote: > Hi Everyone, > > > We submitted a new draft version -15 for multipath extension: > https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ > > > This version contains several modifications regarding to review comments > during the last call: > > > 1. Rename PATH_AVAILABLE and PATH_BACKUP frames to PATH_STATUS_AVAILABLE > and PATH_STATUS_BACKUP frames. > > 2. Connection closure follows RFC 9000. Considering closing and draining > connection states "SHOULD persist for at least three times the current > PTO", please use the largest PTO among all paths. > > 3. If an endpoint sends a PATH_RESPONSE, it MUST be sent on the same path > as used by the packet that contained the PATH_CHALLENGE frame, using a > connection ID associated with the same path ID. > > 4. Fix the example of new path establishment and AEAD nonce calculation. > > 5. Rename transport error codes used in the PATH_ABANDON frame. > > 6. It’s not recommend to send keep-alives as it can create unnecessary > overhead, especially if there’re other actively used paths. > > 7. In the Section of Security Consideration, express the risk of > amplifired DoS attack with Multiple Paths and how to limit it. > > 8. Other small editorial modification. > > > The diff link between -14 and -15: > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-15 > <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 <[email protected]> > Send Time:2025 Jul. 7 (Mon.) 23:24 > To:LIU Yanmei<[email protected]>; "马云飞"<[email protected]>; > Christian Huitema<[email protected]>; Mirja Kuehlewind< > [email protected]>; Olivier Bonaventure< > [email protected]>; Quentin De Coninck< > [email protected]>; "quic-chairs"<[email protected]> > Subject:New Version Notification for draft-ietf-quic-multipath-15.txt > > A new version of Internet-Draft draft-ietf-quic-multipath-15.txt has been > successfully submitted by Mirja Kühlewind and posted to the > IETF repository. > > Name: draft-ietf-quic-multipath > Revision: 15 > Title: Multipath Extension for QUIC > Date: 2025-07-07 > Group: quic > Pages: 38 > URL: https://www.ietf.org/archive/id/draft-ietf-quic-multipath-15.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/ > HTML: > https://www.ietf.org/archive/id/draft-ietf-quic-multipath-15.html > HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-quic-multipath > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-multipath-15 > > 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]), 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 > >
