QUIC Multipath Requirements
draft-huitema-quic-mpath-req-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2018-07-16 (latest revision 2018-01-07) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
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) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-huitema-quic-mpath-req-01.txt
https://www.ietf.org/archive/id/draft-huitema-quic-mpath-req-01.txt
Abstract
This document describes the requirement and plausible architecture of QUIC multipath extensions. While the first version of QUIC is not scheduled to include multipath extensions, there are risks that decisions made in this first version might preclude some options that we may later find attractive. An early review of multipath extension requirements and issues should minimize that risk.
Authors
Christian Huitema (huitema@huitema.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)