The Future With QUIC
summary
QUIC ships TLS inside an encrypted, UDP-based transport to avoid ossification and enable rapid user-space deployment; it delivers zero-RTT transport handshake for substantially lower latencies than TCP+TLS and supports connection migration and lightweight multi-streams. A working demo extracts a server-side self-trace via same QUIC connection so client and server logs correlate without server access. Ongoing projects include the Pico congestion controller, MASQUE (used by Apple Private Relay), and MOQ for media, and multiple QUIC versions already run in parallel on the Internet.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:08What is QUIC
- 3:59QUIC on UDP
- 6:45QUIC value
- 9:58Connection migration
- 11:03Debugging QUIC
- 13:54Server tracing demo
- 14:55QUIC server design
- 15:58QUIC future
- 18:06Conclusion & Q&A
related talks
30mQUIC, in Theory and Practice
30mThere and back again: reinventing UDP streaming with QUIC
54mQUIC illustrated
51mDown the line: Evolving HTTP and making things QUIC
28mHTTP 2.0 and QUIC - protocols of the (near) future
37mHTTP/3: why and where are we?
46mHTTP/3: It's all about the transport!
34mQUIC and HTTP/3: Too Big to Fail?!