What changed
Published in August 2026, RFC 10024 specifies X25519MLKEM768, SecP256r1MLKEM768, and SecP384r1MLKEM1024 for TLS 1.3. It combines classical ECDHE with ML-KEM in named hybrid groups. This gives enterprise architects a standards-track reference for the transport negotiation. Hybrid TLS: RFC 10024 ↗
What it means for an enterprise
Our architectural reading is that procurement can become more precise: ask which group a release negotiates, which network path was tested, and how policy handles an unsupported peer. The word quantum-ready is less useful than a captured negotiation record and a clear minimum policy.
Keep certificate authentication as a separate workstream. A transport migration can protect session confidentiality while the PKI still depends on classical signatures. Likewise, an upgraded gateway says nothing about a downstream origin connection terminated elsewhere.
The next useful action
- Inventory every TLS termination point on a representative application path.
- Choose a pilot cohort with varied client stacks and network inspection.
- Require positive and negative negotiation tests.
- Record certificate schemes separately from key-establishment groups.
- Assign an owner and expiry to compatibility exceptions.
The Antara post-quantum library includes an mTLS sequence, PKI migration gates, and OpenSSL diagnostics to structure that evaluation.