Glonce

IETF freezes TLS 1.2 in RFC 9851, steers PQC to TLS 1.3

policyThe Glonce editorsHacker News🔥49Glonce rating49Impact50Novelty40Relevance55Surprise30Players45Credibility95

The IETF has published RFC 9851, an Internet Standards Track document approved by the IESG and carrying the consensus of the IETF community, which puts TLS 1.2 into a formal feature freeze. From now on, no changes to TLS 1.2 will be approved beyond urgent security fixes, as determined by TLS Working Group consensus, new TLS Exporter Labels, and new Application-Layer Protocol Negotiation (ALPN) Protocol IDs. The freeze applies to TLS only; DTLS, in any version, is untouched.

The document's own reasoning is that TLS 1.3 already fixes most of TLS 1.2's known deficiencies, encrypting more of the traffic so it is not readable by outsiders and dropping cryptographic primitives now considered weak, and that its use is growing. RFC 9851 states plainly that post-quantum cryptography (PQC) will not be specified for TLS 1.2 at any time; anyone who wants to deploy PQC should expect to use TLS 1.3.

The document frames this against the quantum threat: cryptographically relevant quantum computers, once available, are likely to greatly cut the time and effort needed to break RSA, finite-field Diffie-Hellman, or elliptic curve cryptography, the primitives TLS currently relies on. NIST began a multi-year effort to standardize quantum-safe algorithms in 2016, the IETF formed a working group on PQC in its protocols in early 2023, and in 2024 NIST released the ML-KEM, ML-DSA, and SLH-DSA standards. The TLS Working Group's post-quantum work is now focused exclusively on TLS 1.3 or later.

Mechanically, RFC 9851 does not close any TLS registries. Instead, it changes the instructions given to IANA and the TLS Designated Experts, adding a note to most TLS registries (including TLS Cipher Suites, TLS Alerts, TLS Supported Groups, and about twenty others listed in the document) that any entry added after this RFC's approval is intended for TLS 1.3 or later. Two registries, TLS Exporter Labels and TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs, are exempted from the new constraint. The document thanks IANA staff Amanda Baber, David Dong, and Sabrina Tanamal for help revising the relevant section.

The RFC sets no sunset or removal date for TLS 1.2 itself; the freeze covers future changes to the protocol's specification, not a deprecation timeline for its use in the field.

Key facts

  • RFC 9851 freezes TLS 1.2: only urgent security fixes, new TLS Exporter Labels, and new ALPN Protocol IDs will still be approved.
  • The freeze applies to TLS only, not to DTLS in any version.
  • Post-quantum cryptography will not be specified for TLS 1.2 at any time; PQC deployment requires TLS 1.3.
  • No TLS registries are closed; instead, most of them get a note that new entries are for TLS 1.3 or later, with the TLS Exporter Labels and ALPN Protocol IDs registries exempted.
  • No sunset or removal date is set for TLS 1.2 itself, only a freeze on future changes to its specification.

Why it matters

RFC 9851 is the IETF formally closing the book on TLS 1.2's active development, not a deprecation notice. It cements TLS 1.3 as the only protocol version that will keep evolving, including for post-quantum cryptography, and reflects the document's own justification that TLS 1.3 already fixes most of TLS 1.2's known weaknesses and that its adoption is growing.

Who it affects

TLS and DTLS library maintainers, browser and server vendors, and anyone maintaining the affected IANA registries, since new registrations there will now be marked for TLS 1.3 or later by default. It also affects anyone planning to deploy post-quantum cryptography in TLS, since RFC 9851 rules that out for TLS 1.2 entirely.

How to use it

RFC 9851 is a public Internet Standards Track document, published at rfc-editor.org, subject to BCP 78 and the IETF Trust's Legal Provisions; Code Components extracted from it must carry Revised BSD License text. Implementers who still need to submit a change to TLS 1.2 must go through TLS Working Group consensus and show it qualifies as an urgent security fix, a new TLS Exporter Label, or a new ALPN Protocol ID; everything else will not be accepted.

How solid is it

It is as solid as an IETF document gets: an Internet Standards Track RFC that has been through IETF public review and IESG approval, representing IETF community consensus. The content extracted here is the RFC text itself, so the facts above come directly from the primary source rather than a secondary report.

Risks and caveats

The RFC does not set a sunset or removal date for TLS 1.2, so the protocol is not being pulled from the field, only frozen from further specification changes. The two registries exempted from the new note are TLS Exporter Labels and ALPN Protocol IDs, and the text does not mention any browser, vendor, or industry reaction to the freeze.

“Put bluntly, PQC for TLS 1.2 will not be specified at any time; anyone wishing to deploy PQC should expect to use TLS 1.3.”

— RFC 9851