Applying GREASE to TLS Extensibility
draft-ietf-tls-grease-00
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8701.
Expired & archived
|
|
|---|---|---|---|
| Author | David Benjamin | ||
| Last updated | 2017-07-22 (Latest revision 2017-01-18) | ||
| Replaces | draft-davidben-tls-grease | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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 describes GREASE (Generate Random Extensions And Sustain Extensibility), a mechanism to prevent extensibility failures in the TLS ecosystem. It reserves a set of TLS protocol values that may be advertised by clients to ensure servers correctly handle unknown values.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)