Manageability of the QUIC Transport Protocol
draft-kuehlewind-quic-manageability-00
| Document | Type | Replaced Internet-Draft (quic WG) | |
|---|---|---|---|
| Authors | Mirja Kühlewind , Brian Trammell , Dan Druta | ||
| Last updated | 2017-06-15 (Latest revision 2017-03-09) | ||
| Replaces | draft-kuehlewind-quic-appman | ||
| Replaced by | RFC 9312 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-quic-manageability | |
| Consensus boilerplate | Unknown | ||
| 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 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
Brian Trammell
Dan Druta
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)