Fwd: New Version Notification for draft-huitema-quic-mpath-explicit-00.txt

[Christian Huitema <[e-mail]>]

During the meeting in Prague, we discussed the options for identifying 
paths in the multipath draft. The WG decided to study what it would take 
to change the implementation of "path-id" independent form the sequence 
numbers of the connection ids. I tried to write a draft describing a 
"path-id extension" that would extend the multipath draft to use a CID 
independent path id. I think I did a fair spec based on the ideas 
floating around, but hey, I could be wrong. The draft is:

     URL: 
https://www.ietf.org/archive/id/draft-huitema-quic-mpath-explicit-00.txt
     Status: 
https://datatracker.ietf.org/doc/draft-huitema-quic-mpath-explicit/
     HTMLized: 
https://datatracker.ietf.org/doc/html/draft-huitema-quic-mpath-explicit

Please comment either on this list, or maybe on issue 214 in the quic 
multipath GitHub: https://github.com/quicwg/multipath/issues/214

My next step is to implement that in picoquic, to assess the 
implementation issues, perf, etc., and do a comparison with what we 
have. Hopefully that will help us decide one way or another during the 
next QUIC interim.

-- Christian Huitema


-------- Forwarded Message --------
Subject: New Version Notification for 
draft-huitema-quic-mpath-explicit-00.txt
Date: Thu, 09 Nov 2023 20:59:44 -0800
From: [e-mail]
To: Christian Huitema <[e-mail]>

A new version of Internet-Draft draft-huitema-quic-mpath-explicit-00.txt has
been successfully submitted by Christian Huitema and posted to the
IETF repository.

Name:     draft-huitema-quic-mpath-explicit
Revision: 00
Title:    Explicit QUIC Path-ID extension
Date:     2023-11-09
Group:    Individual Submission
Pages:    7
URL: 
https://www.ietf.org/archive/id/draft-huitema-quic-mpath-explicit-00.txt
Status: 
https://datatracker.ietf.org/doc/draft-huitema-quic-mpath-explicit/
HTMLized: 
https://datatracker.ietf.org/doc/html/draft-huitema-quic-mpath-explicit


Abstract:

    The work on QUIC multipath has almost converged, but we are still
    debating how to identify paths.  The draft multipath version 06
    identifies paths explicitly using the sequence number of the
    Connection Identifier used for sending packets on the path.  The WG
    is considering an alternate proposal in which the path ID is
    explicit.  In order to compare the two solutions, we propose here an
    extension to the multipath draft allowing endpoints to negotiate the
    use of explicit sequence numbers.  When the extension is negotiated,
    endpoints announce new connection identifiers using a new
    MP_CONNECTION_ID frame, which carries the parameters of the
    NEW_CONNECTION_ID plus a path ID.  This path ID is used instead of
    the CID sequence number to identify packet number spaces, to create
    encryption nonces, to identify paths in MP_ACK, MP_ABANDON,
    MP_AVAILABLE and MP_STANBY frames, and to perform the logic
    associated with path creation, path CID rotation, and NAT rebinding.
    The draft analyzes the pros and cons of using this extension.  After
    experimentation and analysis, we expect that this extension will be
    either absorbed into a new version of the QUIc multipath draft, or
    abandoned.



The IETF Secretariat