@techreport{kuehlewind-masque-quic-substrate-00,
    number =    {draft-kuehlewind-masque-quic-substrate-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-kuehlewind-masque-quic-substrate/00/},
    author =    {Mirja Kühlewind and Zaheduzzaman Sarker and Thomas Fossati and Lucas Pardue},
    title =     {{Use Cases and Requirements for QUIC as a Substrate}},
    pagetotal = 13,
    year =      2020,
    month =     mar,
    day =       9,
    abstract =  {In situations where direct connectivity is not available or desired, proxies in the network are used to forward and potentially translate traffic. TCP is often used as a proxying or tunneling protocol. QUIC is a new, emerging transport protocol and there is a similar expectation that it too will be used as a substrate once it is widely deployed. Using QUIC instead of TCP in existing scenarios will allow proxying and tunneling services to maintain the benefits of QUIC natively, without degrading the performance and security characteristics. QUIC also opens up new opportunities for these services to have lower latency and better multistreaming support. This document summarizes current and future usage scenarios to derive requirements for QUIC as a substrate and to provide additional considerations for proxy signaling and control protocol as proposed by MASQUE.},
}