Over, Under, Around, and Through: A Detailed Comparison...
summary
Claims that QUIC is "just TCP" or "just HTTP over UDP" are false; QUIC is a transport with multiplexed streams, connection IDs and an optional datagram extension, and HTTP/3 is an application mapping that runs over it. Practical debugging uses Wireshark plus decrypted keys via SSLKEYLOGFILE, qlog structured logs and the qlog analysis tools, and inspecting connection close error codes. MASQUE/extended CONNECT tunnels UDP over HTTP/3 for proxying, with MTU and nesting tradeoffs and a formal load‑balancer draft.
AI-written summary · about
chapters (9)
- 0:00Introduction to QUIC
- 3:00Protocol architecture
- 7:35QUIC internals and personas
- 10:47Handshakes and packet types
- 15:30Debugging and visibility
- 20:47Logging and dissection
- 25:30Connection IDs and streams
- 29:43HTTP/3 and datagrams
- 33:27Tunneling and conclusion
related talks
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
30mThere and back again: reinventing UDP streaming with QUIC
34mSecuring the Next Version of HTTP: How QUIC and HTTP/3 Compare to HTTP/2
46mHTTP/3: It's all about the transport!
37mHTTP/3: why and where are we?
40mHTTP/3 - HTTP over QUIC is the next generation
35mOn QUIC, HTTP/3 and tech stack unification
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?