Conversation

Notices

1. Embed this notice
   Jens Finkhäuser (jens@social.finkhaeuser.de)'s status on Monday, 11-Nov-2024 02:07:02 JST Jens Finkhäuser

   in reply to

   ... what next can you optimize? You can put the key exchange even further up front, which may speed up the QUIC handshake.

   And that only leaves us with DNS as anything that comes earlier. In addition to IP addresses and transport choices, now folk wish to put keys into DNS as well.

   Which may be fine with small Edwards keys. But several KiB of post quantum cryptography key won't fit into a DNS message, which is in practice bound by the size of a UDP datagram.

   So what then - we can't do DNS...

   • Embed this notice
     Jens Finkhäuser (jens@social.finkhaeuser.de)'s status on Monday, 11-Nov-2024 02:07:04 JST Jens Finkhäuser

     ... it's no longer enough to resolve names to IP addresses, you also have to resolve to choices of transport protocols.

     With encrypted transports, you always have a key exchange to deal with, which can be slow.

     The TLS issue is that you have a TCP handshake, which exchanges three packets. Once the TCP session is established, you have a TLS handshake, which is also three or more packets. QUIC adds key information from the start, so you only have one handshake that combines both purposes.

     So...