Sep 18, 2026 · 1 hr 13 min · 11 segments
Q-Day signals the public emergence of a cryptographically relevant quantum computer that can break public key encryption. The date of Q-Day is unknown but the tech industry is making preparations now…
Bill DockeryGuest
Drew Conry-MurrayHost
Scott RobohnHostAll right, so let's get into the second part of this, which is about the impact of post-quantum cryptography on network infrastructure.
Obviously, we've talked about larger key sizes, so that sounds like it's going to have an impact on day-to-day things like handshakes, packet sizes, and so on.
Even MLChem, the 768, by the time it's done, the keys themselves are about 1K size.
We don't get too much detail on this one, but suffice to say that when you start passing these packets, it's going to take potentially two When you used to have 32-byte keys, it's 30 times that now.
And then if you go to even MLChem, the 1024, the actual math that goes in there, when you only have a 1,500-byte payload for Layer 3 inside your Ethernet frames, you're going to need to do two Ethernet frames.
That takes time,
And then when you consider some of these keys, if you tried to send this as a singular packet, the MTU sizes in places, if you send this across, you know, like a carrier network and it's dropping packets because it doesn't like the fragmentation on UDP, because some of this stuff does run on UDP, you see IPsec fail,
I mean, there's a lot of TCP inside of DNS and even in DNSSEC, but there are places where the packet fragmentation, you might be dropping packets.
And just put the two together and all of a sudden, hey, I just tried to get the lock working on my browser.
All right, so let's get into the second part of this, which is about the impact of post-quantum cryptography on network infrastructure.
Obviously, we've talked about larger key sizes, so that sounds like it's going to have an impact on day-to-day things like handshakes, packet sizes, and so on.
Even MLChem, the 768, by the time it's done, the keys themselves are about 1K size.
We don't get too much detail on this one, but suffice to say that when you start passing these packets, it's going to take potentially two When you used to have 32-byte keys, it's 30 times that now.
And then if you go to even MLChem, the 1024, the actual math that goes in there, when you only have a 1,500-byte payload for Layer 3 inside your Ethernet frames, you're going to need to do two Ethernet frames.
That takes time,
And then when you consider some of these keys, if you tried to send this as a singular packet, the MTU sizes in places, if you send this across, you know, like a carrier network and it's dropping packets because it doesn't like the fragmentation on UDP, because some of this stuff does run on UDP, you see IPsec fail,
I mean, there's a lot of TCP inside of DNS and even in DNSSEC, but there are places where the packet fragmentation, you might be dropping packets.
And just put the two together and all of a sudden, hey, I just tried to get the lock working on my browser.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
