QUIC Disable Encryption
draft-banks-quic-disable-encryption-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Nick Banks | ||
| Last updated | 2021-02-12 (Latest revision 2020-08-11) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)