%% You should probably cite draft-lmbdhk-quic-multipath instead of this I-D. @techreport{huitema-quic-mpath-option-01, number = {draft-huitema-quic-mpath-option-01}, 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/01/}, author = {Christian Huitema}, title = {{QUIC Multipath Negotiation Option}}, pagetotal = 12, year = 2021, month = sep, day = 12, abstract = {The initial version of QUIC provides support for path migration. We propose a simple mechanism to support not just migration, but also simultaneous usage of multiple paths. In its simplest form, this mechanisms simply requires that multipath senders keep track of which packet is sent on what path, and use that information to manage congestion control and loss recovery. With that, clients can send data on any validated path, and server on any validated path on which the client recently sent non-probing packets. A more sophisticated mechanism can be negotiated to explicitly manage paths and packet scheduling.}, }