Hacker News Reader

See also DNS over QUIC.

Somewhat tangential: HTTP/3, which will also be using QUIC

https://tools.ietf.org/html/draft-ietf-quic-http-13

Isn't HTTP/3 just the name for IETF's QUIC?

https://news.ycombinator.com/item?id=18427795

There's QUIC (protocol) and HTTP/3 (HTTP over QUIC). DNS over QUIC uses the first but not the second.

QUIC (Quick UDP Internet Connections) is a protocol derived from Google's Speedy project. Another protocol would use QUIC to initiate a handshake between server and client. The cool thing is that it only takes one UDP packet to do what TCP does in the typical SYN/SYN-ACK/ACK.

Well, it's not quite exactly the same thing as the 3-way handshake over a single packet.

The 3-way handshake ensures that both ends are able to send traffic to their counterpart. Just because i receive a packet doesn't mean I can send one back.

Perhaps a better way to phrase it, is that the 3way handshake does not need to be completed before sending data.

Couldn't this mean massive amplification attacks?

HTTPS isn't only used for webapps. It's widely used for APIs from mobile phone apps (for example). There are also a ton of libraries etc. for handling HTTP and HTTPS making it easy to adopt.

Reply on news.ycombinator.com