QUIC: A UDP-Based Multiplexed and Secure Transport
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://ipfyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://ipfyi.com/entity//Add a dynamic SVG badge to your README or docs.
[](https://ipfyi.com/entity//)Use the native HTML custom element.
J. Iyengar, M. Thomson · 2021-05
Abstract
QUIC is a new transport protocol designed to reduce latency compared to TCP and TCP+TLS. QUIC is built on UDP and integrates TLS 1.3 cryptography directly into the handshake, enabling 0-RTT or 1-RTT connection establishment. It supports multiple independent streams over a single connection, eliminating head-of-line blocking, and provides connection migration so that connections survive network changes such as switching from Wi-Fi to cellular.
Why This RFC Matters
QUIC represents the most significant transport layer innovation since TCP, developed originally by Google and subsequently standardized by the IETF. By operating over UDP and embedding TLS, QUIC eliminates the separate TLS handshake round trip, reducing connection establishment latency by 50-100ms in typical scenarios. Its stream multiplexing without head-of-line blocking addresses one of the key performance problems of HTTP/2 over TCP. QUIC is the mandatory transport for HTTP/3 (RFC 9114), and is now used by Google, Meta, Cloudflare, and other major platforms to serve a significant fraction of Internet traffic. Its design also inspires next-generation protocols for gaming, video conferencing, and real-time applications.