RFC 9958: Post-Quantum Cryptography for Engineers
In plain English — editorial summary, not part of the RFC
The advent of a cryptographically relevant quantum computer (CRQC) would render state-of-the-art, traditional public key algorithms deployed today obsolete, as the mathematical assumptions underpinning their security would no longer hold. To address this, protocols and infrastructure must transition to post-quantum algorithms, which are designed to resist both traditional and quantum attacks. This document explains why engineers need to be aware of and understand post-quantum cryptography (PQC), and it details the impact of CRQCs on existing systems and the challenges involved in transitioning to post-quantum algorithms. Unlike previous cryptographic updates, this shift may require significant protocol redesign due to the unique properties of post-quantum algorithms.
Document record
- Document ID
- RFC9958
- Published
- June 2026
- Authors
- A. Banerjee; T. Reddy.K; D. Schoinianakis; T. Hollebeek; M. Ounsworth
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 42
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9955Hybrid Signature SpectrumsCurrent
July 2026
- RFC 9964ML-DSA for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)Current
May 2026
- RFC 9980Post-Quantum Cryptography in OpenPGPCurrent
June 2026
- RFC 9794Terminology for Post-Quantum Traditional Hybrid SchemesCurrent
June 2025
- RFC 9370Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
May 2023
- RFC 9954Hybrid Key Exchange in TLS 1.3Current
July 2026
- RFC 9963Legacy RSASSA-PKCS1-v1_5 Code Points for TLS 1.3Current
April 2026
- RFC 9965The eap.arpa. Domain and Extensible Authentication Protocol (EAP) ProvisioningCurrent
May 2026
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?