RFC 9851: TLS 1.2 is in Feature Freeze
In plain English — editorial summary, not part of the RFC
Use of TLS 1.3, which fixes some known deficiencies in TLS 1.2, is growing. This document specifies that no changes will be approved for TLS 1.2 outside of urgent security fixes (as determined by TLS Working Group consensus), new TLS Exporter Labels, and new Application-Layer Protocol Negotiation (ALPN) Protocol IDs. This applies to TLS only; it does not apply to DTLS (in any DTLS version).
Document record
- Document ID
- RFC9851
- Published
- July 2026
- Authors
- R. Salz; N. Aviram
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9852New Protocols Using TLS Must Require TLS 1.3Current
July 2026
- RFC 9850The SSLKEYLOGFILE Format for TLSCurrent
July 2026
- RFC 9765RADIUS/1.1: Leveraging Application-Layer Protocol Negotiation (ALPN) to Remove MD5Current
April 2025
- RFC 9662Updates to the Cipher Suites in Secure SyslogCurrent
October 2024
- RFC 9162Certificate Transparency Version 2.0Current
December 2021
- RFC 9155Deprecating MD5 and SHA-1 Signature Hashes in TLS 1.2 and DTLS 1.2Current
December 2021
- RFC 9149TLS Ticket RequestsCurrent
April 2022
- RFC 8996Deprecating TLS 1.0 and TLS 1.1Current
March 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?