@techreport{gage-quicmp-pathmodel-00,
    number =    {draft-gage-quicmp-pathmodel-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-gage-quicmp-pathmodel/00/},
    author =    {Bill Gage},
    title =     {{An Alternate Path Model for Multipath QUIC}},
    pagetotal = 14,
    year =      2023,
    month =     nov,
    day =       11,
    abstract =  {The path model used in the current MPQUIC draft binds a connection identifier to a path. In fact, the sequence number of a connection identifier is used as an implicit path identifier. This has a number of consequences that may cause MPQUIC to diverge from the principles of RFC9000. One of these consequences, for example, is to associate each connection with a different application data packet number space rather than maintaining a single application data packet number space across all connections as defined in RFC9000. This document proposes a different path model for Multipath QUIC using explicit path identifiers, enabling a multipath management framework that retains the principles and operations of RFC9000.},
}