<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.tiesel-quic-unreliable-streams" target="https://datatracker.ietf.org/doc/html/draft-tiesel-quic-unreliable-streams-01">
   <front>
      <title>Considerations for Unreliable Streams in QUIC</title>
      <author initials="P. S." surname="Tiesel" fullname="Philipp S. Tiesel">
         <organization>TU Berlin</organization>
      </author>
      <author initials="M." surname="Palmer" fullname="Mirko Palmer">
         <organization>TU Berlin</organization>
      </author>
      <author initials="B." surname="Chandrasekaran" fullname="Balakrishnan Chandrasekaran">
         <organization>TU Berlin</organization>
      </author>
      <author initials="A." surname="Feldmann" fullname="Anja Feldmann">
         <organization>TU Berlin</organization>
      </author>
      <author initials="J." surname="Ott" fullname="Joerg Ott">
         <organization>TU Munich</organization>
      </author>
      <date month="October" day="30" year="2017" />
      <abstract>
	 <t>   This memo outlines how to support unreliable streams as well as
   partially-reliable streams within QUIC.  The intention of this
   document is to collect requirements and considerations, to frame the
   design space, and to give an example how unreliable stream support
   could be realized.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-tiesel-quic-unreliable-streams-01" />
   
</reference>
