@techreport{huitema-quic-mpath-explicit-00,
    number =    {draft-huitema-quic-mpath-explicit-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-huitema-quic-mpath-explicit/00/},
    author =    {Christian Huitema},
    title =     {{Explicit QUIC Path-ID extension}},
    pagetotal = 7,
    year =      2023,
    month =     nov,
    day =       9,
    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.},
}