QUIC

QUIC's Architecture: UDP Without UDP's Drawbacks

QUIC is a transport protocol developed by Google and standardized as RFC 9000. It runs over UDPUser Datagram Protocol. A connectionless transport protocol that sends datagrams without establishing a connection or guaranteeing delivery. Faster than TCP, it is preferred for real-time applications like DNS queries, VoIP, gaming, and streaming. to avoid TCPTransmission Control Protocol. A reliable, connection-oriented transport protocol that guarantees ordered, error-checked delivery of data through three-way handshakes, acknowledgments, and retransmission. The foundation of HTTP, SSH, and most internet services.'s connection establishment overhead, but reimplements reliability, ordering, flow control, and congestion control in userspace. The critical innovation is 0-RTT resumption — a returning client can send application data in the very first packet, eliminating the TCP + SSL/TLSSecure Sockets Layer / Transport Layer Security. Cryptographic protocols that provide encrypted, authenticated communication over a network. SSL is deprecated; modern implementations use TLS 1.2 or TLS 1.3. handshake latency that plagues standard HTTPSHTTP Secure. The encrypted version of HTTP that uses TLS to protect data in transit between a browser and a web server. Identified by the padlock icon in browsers and the https:// URL scheme..

Head-of-Line Blocking Elimination

QUIC multiplexes multiple streams within a single connection without head-of-line blocking. In HTTP over TCP, a lost packet stalls all streams until retransmission completes. QUIC's streams are independent — a lost packet in stream A does not delay stream B. This makes HTTP/3 (which runs exclusively over QUIC) dramatically faster on lossy networks like mobile cellular.

Deployment and Security

QUIC encrypts everything — including connection metadata — using TLS 1.3 keys negotiated during the handshake. Middleboxes (firewalls, proxy servers) cannot inspect or modify QUIC traffic beyond UDP port 443. This creates tension with enterprise security: WAFWeb Application Firewall. A security layer that filters, monitors, and blocks HTTP/HTTPS traffic to and from a web application, protecting against attacks like SQL injection, XSS, and CSRF at the application layer. systems that rely on deep packet inspection cannot inspect QUIC traffic without purpose-built support. Many enterprise networks block UDP 443 to force fallback to TCP-based HTTP/2, at the cost of QUIC's performance benefits.