%% You should probably cite draft-lmbdhk-quic-multipath instead of this I-D.
@techreport{huitema-quic-mpath-option-00,
    number =    {draft-huitema-quic-mpath-option-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-option/00/},
    author =    {Christian Huitema},
    title =     {{QUIC Multipath Negotiation Option}},
    pagetotal = 8,
    year =      2020,
    month =     oct,
    day =       21,
    abstract =  {The initial version of QUIC provides support for path migration. In this draft, we argue that there is a very small distance between supporting path migration and supporting simulatneous traffic on multipath. Instead of using an implicit algorithm to discard unused paths, we propose a simple option to allow explicit management of active and inactive paths. Once paths are explicitly managed, pretty much all other requirements for multipath support can be met by appropriate algorithms for scheduling transmissions on specific paths. These algorithms can be implemented on the sender side, and do not require specific extensions, except maybe a measurement of one way delays.},
}