RFC 8701: Applying Generate Random Extensions And Sustain Extensibility (GREASE) to TLS Extensibility
In plain English — editorial summary, not part of the RFC
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 to ensure peers correctly handle unknown values.
Document record
- Document ID
- RFC8701
- Published
- January 2020
- Authors
- D. Benjamin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8473Token Binding over HTTPCurrent
October 2018
- RFC 8472Transport Layer Security (TLS) Extension for Token Binding Protocol NegotiationCurrent
October 2018
- RFC 8471The Token Binding Protocol Version 1.0Current
October 2018
- RFC 8940Extensible Authentication Protocol (EAP) Session-Id Derivation for EAP Subscriber Identity Module (EAP-SIM), EAP Authentication and Key Agreement (EAP-AKA), and Protected EAP (PEAP)Current
October 2020
- RFC 8449Record Size Limit Extension for TLSCurrent
August 2018
- RFC 8996Deprecating TLS 1.0 and TLS 1.1Current
March 2021
- RFC 9149TLS Ticket RequestsCurrent
April 2022
- RFC 9155Deprecating MD5 and SHA-1 Signature Hashes in TLS 1.2 and DTLS 1.2Current
December 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?