Birth of the Post-Quantum Internet
summary
Cloudflare reports serving ~20% of domains and handling ~46M HTTP requests/sec, and shows post‑quantum key agreement (hybrid Kyber + classical) already on ~20–35% of incoming TLS handshakes with performance near classical after fixing middlebox fragmentation bugs. Post‑quantum signatures remain hard: common options like Dilithium2 add roughly 17 KB to certificate chains, causing ~15–20% TLS handshake slowdowns, chain size breakpoints at ~10 KB and ~30 KB, extra round trips, and wide ecosystem changes (CAs, HSMs, CT logs) before practical web deployment.
AI-written summary · about
chapters (6)
- 0:00Welcome
- 3:58Post-quantum migration status
- 11:10Key agreement migration
- 18:58Signature migration risks
- 21:08DNSSEC and advanced crypto
- 22:14Q&A
related talks
29mWhy the Internet isn’t ready for Post-Quantum Certificates
35mLessons Learned from Testing Millions of Servers for Post-Quantum Compatibility
01h 05mChallenges and Opportunities from Quantum-Safe Cryptography
15mSecuring Cloud Native Infra for the Post-Quantum Era
27mTurning Quantum Threats into Opportunities: Modernizing WebPKI with QUIC and Metrics-Driven Insights
30mNavigating the Quantum Readiness Journey: Securing Kubernetes with Quantum-Resis...
34mBeyond Classical Cryptography: Building Quantum-Resistant Cloud Native Infrastructure With SPIFFE
44mPost-quantum cryptography migration strategy for cloud services