QUIC illustrated
summary
Explains what QUIC actually does and what was tested: observed Internet share ~7–10% and Google ~35% QUIC traffic, captured a Chrome/alt‑svc session and exported a JSON qlog to inspect the handshake, streams and frames, and verified 0‑RTT + early data pitfalls, first QUIC packet ≥1200 bytes (amplification mitigation) and connection migration via Connection ID. Notes practical issues: middleboxes still drop QUIC, packet loss and replay handling differ from TCP, resource‑exhaustion risks from cheap streams, and several server implementations (≈9k to ≈130k LOC) exist.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:53What is QUIC and its benefits
- 5:10HTTP/2 problems and solutions
- 9:04QUIC solves head-of-line blocking
- 14:06QUIC over UDP
- 20:15QUIC in action demo
- 27:09QUIC packet structure
- 34:10Flow control in QUIC
- 39:35Security and performance issues
- 44:11QUIC in Linux kernel
- 47:23Q&A
related talks
19mThe Future With QUIC
43mDeploying and Debugging HTTP/3
40mHTTP/3 - HTTP over QUIC is the next generation
34mQUIC and HTTP/3: Too Big to Fail?!
38mOver, Under, Around, and Through: A Detailed Comparison...
35mOn QUIC, HTTP/3 and tech stack unification
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
42mMQTT over QUIC: Opportunities and Challenges