Proxying HTTP/3 (QUIC) Using CONNECT-UDP with Envoy

on YouTube ↗31m

" summary

Envoy implements IETF CONNECT-UDP (RFC 9298) and HTTP datagrams/capsules (RFC 9221/9227/9297) to tunnel QUIC/HTTP/3 over HTTP, normalizing extended CONNECT to upgrade and rewriting host/path so routing works. It creates a UDP upstream socket per target, maps downstream streams to sockets, and uses HTTP datagrams/capsules to avoid nested loss recovery and head‑of‑line blocking. Demo proxies to google youtube and Cloudflare succeed, and this is the first open-source Envoy support enabling single‑hop H3 multiplexing and two‑hop privacy patterns like iCloud Private Relay.

AI-written summary · about

" chapters (10)

1. 0:00Proxying HTTP/3 with CONNECT-UDP
2. 1:51Limitations of existing protocols
3. 4:44Why CONNECT-UDP was developed
4. 6:51Envoy changes for CONNECT-UDP
5. 11:57Data path with HTTP datagrams
6. 17:23Live demo of CONNECT-UDP
7. 19:58Benefits of HTTP/3 proxying
8. 22:07Two-hop proxying for privacy
9. 23:54Conclusion and future impact
10. 24:38Q&A

" related talks

• 20mHTTP/3 in Envoy: End to End AccelerationAlyssa Wilk, Ryan Hamilton · EnvoyCon North America 2021
• 34mEnvoy Q&AMatt Klein, Harvey Tuch · KubeCon + CloudNativeCon North America 2020 Virtual
• 40mHTTP/3 - HTTP over QUIC is the next generationDaniel Stenberg · Full Stack Fest 2019
• 43mDeploying and Debugging HTTP/3Robin Marx · SREcon23 Europe/Middle East/Africa
• 37mHTTP/3: why and where are we?Daniel Stenberg · Øredev 2023
• 30mThere and back again: reinventing UDP streaming with QUICLucas Pardue · Demuxed 2019
• 10mLightning Talk: Envoy Upstream EnhancementsAlyssa Wilk · EnvoyCon North America 2022
• 51mHTTP/3 and QUIC: Who, what, where, when and, WHY?Robin Marx · Devoxx Belgium 2024