TLS Performance: QUIC and HTTP/3
Explore how QUIC integrates TLS 1.3 at the transport layer and what it means for performance and security.
Head-of-Line Blocking in TCP
HTTP/2 multiplexes multiple streams over a single TCP connection, solving HTTP/1.1's per-connection head-of-line blocking. However, TCP itself causes head-of-line blocking at the transport layer: if one TCP segment is lost, all data behind it in the queue waits for retransmission, blocking all HTTP/2 streams simultaneously. A 1% packet loss can degrade HTTP/2 performance below HTTP/1.1 with multiple connections. QUIC (Quick UDP Internet Connections) solves this by implementing multiplexed streams over UDP, where stream-level loss recovery does not block other streams.
QUIC Architecture
QUIC is a transport protocol built on UDP, developed by Google (2012-2015) and standardized by IETF as RFC 9000 (2021). QUIC integrates TLS 1.3 at the transport layer — there is no separate TLS handshake on top of QUIC; TLS is woven into the QUIC handshake itself. QUIC provides: multiplexed streams without head-of-line blocking, connection migration (maintaining the connection when switching networks, e.g., WiFi to LTE), 0-RTT connection establishment for repeat connections, and built-in loss detection and congestion control. HTTP/3 (RFC 9114) is HTTP semantics over QUIC streams.