LIVE Q&A #1
summary
Multiple QUIC versions already coexist so kernel implementations do not kill agility but slow rollout of specific versions; interoperability relies on spec fixes. DSR separates front-end/back-end logic so backends are simple writers, uses independent streams and per-packet encryption to simplify distributed TLS and offload. Debugging relies on qlog tracing with added DSR events. Jumpstart is deployed in a backbone assuming stable paths and static capacity, jumpstart sets initial congestion window and preserves cubic fairness; for Internet use it proposes opaque tokens and can work with BBR. NIC offloads focus on encryption and pacing to keep QUIC malleable.
AI-written summary · about
chapters (11)
- 0:00Event introduction
- 0:45Protocol agility and kernel
- 3:55User vs kernel performance
- 6:00DSR design and complexity
- 8:50Debugging DSR errors
- 13:53Deployment challenges
- 16:44Quick vs TCP BBR
- 18:09TLS integration in Quick
- 19:32Fairness of Quick flows
- 20:57Offloading DSR to SmartNICs
- 24:25Closing remarks
related talks
17mQDSR: Accelerating Layer-7 Load Balancing by Direct Server Return with QUIC
54mQUIC illustrated
43mDeploying and Debugging HTTP/3
34mEnvoy Q&A
34mQUIC and HTTP/3: Too Big to Fail?!
30mOffloading QUIC Encryption to Enabled NICs
22mQ&A Session 2 – Bharat Parekh
35mOn QUIC, HTTP/3 and tech stack unification