3 ms·
Small DNS queries and answers fit in one UDP packet, but larger ones don't and have to be retried as TCP. HTTPS/2 over TLS 1.3 (which is the baseline you shoul
by tialaramex 7y ago
Small DNS queries and answers fit in one UDP packet, but larger ones don't and have to be retried as TCP.
HTTPS/2 over TLS 1.3 (which is the baseline you should assume for these relatively new services) is one TCP setup plus potentially 0-RTT TLS on all but the first visit.
0-RTT is safe here because a DNS query is just a question with no side effects. Replay attacks (the risk 0-RTT incurs) don't do anything:
Gumby: "What is the IPv4 address of news.ycombinator.com?" encrypted so that only DoH Server and you can read it
Server: "209.216.230.240" encrypted so that only Gumby and the DoH server can read it
Attacker: Replays Gumby's packet with no knowledge what it means
Server: Same reply, also unintelligible to attacker just like the original
For HTTPS/3 (over QUIC rather than TLS+TCP) it's UDP so the only "overhead" is from the crypto setup which is modest on even a relatively weak machine.
- gumby 7y agoThanks. I hadn't followed the development of 0-RTT which allows the server to tear down the connection.