PQC Standardization at the Internet Engineering Task Force (IETF)
summary
Registers for ML-DSA/SLH-DSA/ML-KEM and LMS/XMSS/composite hybrids exist but many code points still need RFCs; TLS hybrids are already deployed in Chrome while pure ML-DSA/TLS drafts are missing. Critical engineering issues remain: FIPS 203 allows both seed and expanded private-key formats causing PKCS#11/PKCS#12 mismatches, CSR enrollment cannot be signed with KEM keys so certificate enrollment flows need redesign, ACME and IoT workflows require challenge-response or new CSR patterns, and ML-KEM packet sizes break some VPN/IPsec handshakes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:04PQC standardization overview
- 3:36Protocols needing updates
- 6:26RFC standardization process
- 8:10LAMPS PQC status
- 10:14Private key format issues
- 13:09Certificate enrollment for ML-KEM
- 17:01TLS integration challenges
- 19:05IPsec and VPN updates
- 20:52OpenPGP and JWT standardization
- 22:15FIPS compliance concerns
- 25:28Q&A
related talks
35mThe internet is ready for some PQC certificates
59mPost-quantum cryptography for .NET developers
32mPQC in OpenSSL Library
13mNavigating the Quantum Readiness Journey: Open-Source Cryptography, PKI and Signing Tools
44mPQC at the Internet Engineering Task Force IETF
27mImplementing Post Quantum algorithms in PKCS #11
24mTransitioning to Post-Quantum Cryptography in IAM
27mThe PQC Landscape: Protocols and Standards