AIBRIEF
The IETF (Internet Engineering Task Force), the internet's standards setting body, has put TLS 1.
When you load an HTTPS page, your browser usually negotiates one of two versions of the encryption underneath: the older TLS 1.2, or the newer TLS 1.3. The internet's standards body has now decided the older one is finished taking on new features.
RFC 9851, published in July 2026 on the IETF Standards Track, puts TLS 1.2 in "feature freeze." The change is process-level, not a wire-level break. HTTPS still works the same on every server using TLS 1.2.
What changes is what the IETF will accept going forward: nothing, except for three narrow categories. Urgent security fixes, as determined by working group consensus, can still land. So can new TLS Exporter Labels and new ALPN Protocol IDs, the identifiers browsers and servers use to agree on which application protocol runs over the encrypted tunnel.
The rationale, in the RFC's own words: TLS 1.3 fixes most known deficiencies with TLS 1.2 (weaker cryptographic primitives, less encrypted surface, weaker security proofs) and adoption is growing. Reviewers noted that NIST's 2024 standardization of ML-KEM, ML-DSA, and SLH-DSA made post-quantum migration another reason operators should be on 1.3.
The freeze covers TLS only. DTLS, the datagram variant used in some real-time and VPN traffic, is explicitly excluded. The RFC does not measure TLS 1.2's current share of internet traffic or vendor migration timelines; that accounting falls to deployment tracking outside the standards body.