Applying GREASE to TLS Extensibility
draft-davidben-tls-grease-01
| Document | Type |
Replaced Internet-Draft
(candidate for tls WG)
Expired & archived
|
|
|---|---|---|---|
| Author | David Benjamin | ||
| Last updated | 2016-12-08 (Latest revision 2016-09-02) | ||
| Replaced by | RFC 8701 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-tls-grease | |
| 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.)