LIVE Q&A #2
summary
Live Q&A focuses on practical QUIC and HTTP/3 issues: adoption grows via browser defaults and DNS service records but many systems stay on HTTP/1.1 for simplicity; zero‑RTT gives near‑theoretical latency but carries zero-RTT replay risk so only idempotent requests are recommended; TLS 1.3 half‑RTT lets servers send early data without resumption; implementers iterate—use RFC 9000 and 9002 guidance, robust testing and server‑side logs at scale; debugging relies on qlog crate for quiche and sampled production traces.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:04QUIC and HTTP/3 adoption
- 6:43Zero RTT limits
- 9:11QUIC implementation complexity
- 11:38Debugging QUIC with qlog
- 15:54Protocol debugging importance
- 20:31Zero RTT and server data
- 22:38Zero RTT security
related talks
43mDeploying and Debugging HTTP/3
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?
34mQUIC and HTTP/3: Too Big to Fail?!
34mHTTP/3 is coming
53mQUIC, TLS 1.3, DNS-over-HTTPS, everywhere next
46mHTTP/3: It's all about the transport!