Network Path Requirements for QUIC
draft-wing-quic-network-req-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2016-12-17 (latest revision 2016-06-14) | ||
| 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-wing-quic-network-req-00.txt
Abstract
As QUIC is deployed in more networks, some existing network path infrastructure will need to be updated. This document describes a few ways QUIC might be modified to make these updates possible and palatable to the developers and operators that will need to make the changes.
Authors
Dan Wing
(dwing@cisco.com)
Joe Hildebrand
(jhildebr@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)