Manageability of the QUIC Transport Protocol
draft-kuehlewind-quic-manageability-00
| Document | Type | Replaced Internet-Draft (quic WG) | |
|---|---|---|---|
| Last updated | 2017-06-15 (latest revision 2017-03-09) | ||
| Replaces | draft-kuehlewind-quic-appman | ||
| Replaced by | draft-ietf-quic-manageability | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-quic-manageability | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-kuehlewind-quic-manageability-00.txt
Abstract
This document discusses manageability of the QUIC transport protocol, focusing on caveats impacting network operations involving QUIC traffic. Its intended audience is network operators, as well as content providers that rely on the use of QUIC-aware middleboxes, e.g. for load balancing.
Authors
Mirja Kühlewind
(mirja.kuehlewind@tik.ee.ethz.ch)
Brian Trammell
(ietf@trammell.ch)
Dan Druta
(dd5826@att.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)