Considerations for Unreliable Streams in QUIC
draft-tiesel-quic-unreliable-streams-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2018-05-03 (latest revision 2017-10-30) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-tiesel-quic-unreliable-streams-01.txt
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 Tiesel
(philipp@inet.tu-berlin.de)
Mirko Palmer
(mirko@inet.tu-berlin.de)
Balakrishnan Chandrasekaran
(balac@inet.tu-berlin.de)
Anja Feldmann
(anja@inet.tu-berlin.de)
Joerg Ott
(ott@in.tum.de)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)