%% You should probably cite draft-jones-tsvwg-transport-for-satellite instead of this I-D.
@techreport{kuhn-quic-4-sat-03,
    number =    {draft-kuhn-quic-4-sat-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kuhn-quic-4-sat/03/},
    author =    {Nicolas Kuhn and Gorry Fairhurst and John Border and Stephan Emile},
    title =     {{QUIC for SATCOM}},
    pagetotal = 12,
    year =      2020,
    month =     jan,
    day =       16,
    abstract =  {QUIC has been designed for use across Internet paths. Initial designs of QUIC have focussed on common deployment scenarios for web traffic and have not focussed on the performance when using a path with a large Bandwidth-Delay Product (BDP). A path can combine satellites network segment together with a wide variety of other network technologies (Ethernet, cable modems, WiFi, cellular, radio links, etc): this complicates the characteristics of the end-to-end path. One example of such a scenario occurs when a satellite communication (SATCOM) system is used to provide all or a part of the end-to-end path. If this is not addressed, the end-to-end quality of experience can be degraded. This memo identifies the characteristics of a SATCOM link that impact the operation of the QUIC transport protocol. It proposes regression tests to evaluate QUIC over SATCOM links. It discusses how to ensure acceptable protocol performance.},
}