Down the line: Evolving HTTP and making things QUIC
summary
QUIC moves HTTP off TCP onto UDP to avoid TCP head‑of‑line blocking, implements multiplexed streams, built‑in congestion control and ACK/timer loss detection, and bundles TLS 1.3 so handshakes drop to one RTT or zero round-trip resume for repeat connections. Google reports 15–18% fewer rebuffer events on YouTube and 3.6–8% search latency improvements; QUIC already carries about 4–7% of Internet traffic. Ossification by middleboxes motivates encrypting headers so the transport can evolve.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 1:12OSI model
- 3:22Latency
- 6:55Access networks
- 7:37Data
- 8:42HTTP
- 11:32Pipelining
- 12:41Pipelining disadvantages
- 13:20Roundtrips
- 14:56Speedy
- 15:31Header compression
- 16:38IETF
- 18:02HTTP Header Compression
- 19:09HTTP 2 Encryption
- 20:39Packet Loss
- 21:26Headofline Blocking
- 23:24Supermarket analogy
- 24:14QUIC
- 25:24QUIC goals
- 26:08Ossification
- 27:29Enterprise filters
- 28:17TCP and UDP
- 30:15UDP as a transport layer
- 30:43TCP as a transport layer
- 31:33Google QUIC
- 33:08Streams
- 33:59HTTP Over Quick
- 34:29Connection Establishment
- 35:06Round Trips
- 37:02Quick Recovery
- 37:57Loss Detection
- 41:33Safety
- 42:25HTTP and TLS
- 43:37Attack Mitigations
- 44:28Status and Stats
- 45:11Quick Deployment
- 47:52IETF meeting
related talks
30mQUIC, in Theory and Practice
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
40mHTTP/3 - HTTP over QUIC is the next generation
30mThere and back again: reinventing UDP streaming with QUIC
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
19mThe Future With QUIC
46mHTTP/3: It's all about the transport!
34mSecuring the Next Version of HTTP: How QUIC and HTTP/3 Compare to HTTP/2