Considerations for Unreliable Streams in QUIC
draft-tiesel-quic-unreliable-streams-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Philipp S. Tiesel , Mirko Palmer , Balakrishnan Chandrasekaran , Anja Feldmann , Joerg Ott | ||
| Last updated | 2018-05-03 (Latest revision 2017-10-30) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Philipp S. Tiesel
Mirko Palmer
Balakrishnan Chandrasekaran
Anja Feldmann
Joerg Ott
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)