QUIC Disable Encryption
draft-banks-quic-disable-encryption-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Nick Banks | ||
| Last updated | 2021-02-12 (latest revision 2020-08-11) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
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-banks-quic-disable-encryption-00.txt
https://www.ietf.org/archive/id/draft-banks-quic-disable-encryption-00.txt
Abstract
The disable_1rtt_encryption transport parameter can be used to negotiate the disablement of encryption on 1-RTT packets, allowing for reduced CPU load and improved performance. This extension is only meant to be used in environments where both endpoints completely trust the path between themselves; not, for instance, on the open internet.
Authors
Nick Banks (nibanks@microsoft.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)