<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.kuehlewind-masque-quic-substrate" target="https://datatracker.ietf.org/doc/html/draft-kuehlewind-masque-quic-substrate-00">
   <front>
      <title>Use Cases and Requirements for QUIC as a Substrate</title>
      <author initials="M." surname="Kühlewind" fullname="Mirja Kühlewind">
         <organization>Ericsson</organization>
      </author>
      <author initials="Z." surname="Sarker" fullname="Zaheduzzaman Sarker">
         <organization>Ericsson</organization>
      </author>
      <author initials="T." surname="Fossati" fullname="Thomas Fossati">
         <organization>Arm</organization>
      </author>
      <author initials="L." surname="Pardue" fullname="Lucas Pardue">
         <organization>Cloudflare</organization>
      </author>
      <date month="March" day="9" year="2020" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-kuehlewind-masque-quic-substrate-00" />
   
</reference>
