Skip to content
IETF Publishes RFCs on Post-Quantum Cryptography and TLS 1.3 Standards

IETF Publishes RFCs on Post-Quantum Cryptography and TLS 1.3 Standards

First seen 15 Oct 2026, 09:36 UTC •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 16, 2026 at 07:37 UTC
  • •RFC 9794 defines terminology for hybrid cryptographic schemes.
  • •RFC 9851 restricts changes to TLS 1.2, focusing on urgent security fixes.
  • •Both RFCs are informational and part of IETF's ongoing standards development.

On October 15, 2026, the IETF published RFC 9794, defining terminology for hybrid cryptographic schemes that combine post-quantum and traditional asymmetric algorithms. This document aims to provide clarity and consistency across various protocols and organizations. Additionally, RFC 9851 was released, indicating that TLS 1.2 will receive no changes except for urgent security fixes, while the use of TLS 1.3 continues to grow. These documents are informational and do not constitute Internet Standards. They represent the consensus of the IETF community and have been approved by the Internet Engineering Steering Group (IESG). No specific vulnerabilities or active threats were reported in relation to these documents.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-10-15
RFC 9794 published
IETF published RFC 9794 to define terminology for hybrid cryptographic schemes, aiding clarity in post-quantum cryptography.
www.rfc-editor.org
2026-10-15
RFC 9851 published
RFC 9851 specifies that no changes will be made to TLS 1.2 except for urgent security fixes, promoting TLS 1.3 usage.
www.rfc-editor.org

More articles in this cluster (2)

Common questions

What is RFC 9794 about?
RFC 9794 defines terminology for hybrid cryptographic schemes that combine post-quantum and traditional algorithms.
What changes are being made to TLS 1.2?
RFC 9851 states that TLS 1.2 will only receive urgent security fixes and no other changes will be approved.
Are there any known vulnerabilities related to these RFCs?
No specific vulnerabilities or active threats were reported in relation to the publication of these RFCs.