Skip to content
AdminKit

QUIC

What is QUIC?

QUIC, defined in RFC 9000, is a transport protocol that runs over UDP and builds the TLS 1.3 handshake into connection setup, avoiding the head-of-line blocking TCP-based HTTP/2 can't escape. AdminKit's TLS check guide explains the handshake version your tool reports, over TCP, distinct from the one QUIC carries over UDP.

By AdminKit team, Netbase JSC · Updated

QUIC, defined in RFC 9000 — also tracked on its IETF Datatracker page — is a transport protocol that runs over UDP instead of TCP and builds the TLS 1.3 handshake into establishing a connection, rather than layering TLS on top of a separate transport handshake. As MDN’s glossary entry puts it, “QUIC integrates the TLS handshake into the initial QUIC handshake, reducing the number of messages that must be exchanged during setup.” A client and server exchange cryptographic and transport parameters together, so a new connection to an already-known server can often send encrypted application data after a single round trip (0-RTT), instead of waiting through a separate TCP handshake and TLS handshake first. QUIC multiplexes many independent streams over one connection, and because loss recovery happens per stream rather than once for the whole connection, a lost packet only stalls the stream it belonged to instead of blocking every other stream in flight — the head-of-line-blocking problem TCP-based HTTP/2 cannot avoid. QUIC also identifies a connection independently of the underlying IP address and port, so a connection can survive a client switching networks, such as moving from WiFi to mobile data, without being torn down and renegotiated from scratch. HTTP/3 is the application protocol built on top of QUIC. Server software has followed: nginx’s QUIC and HTTP/3 documentation states that support for both protocols has been available since nginx 1.25.0 and is included in its Linux binary packages. Rather than relying on ICMP the way classic Path MTU Discovery does, QUIC probes the largest packet size a path can carry directly at the transport layer (DPLPMTUD, RFC 8899), which keeps working even when a network silently drops the ICMP messages PMTUD needs.

AdminKit groups qUIC under its machine protocols cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

Why doesn't a lost packet stall every stream in a QUIC connection?

QUIC multiplexes many independent streams over one connection, and loss recovery happens per stream rather than once for the whole connection, so a lost packet only stalls the stream it belonged to -- avoiding the head-of-line-blocking problem TCP-based HTTP/2 can't escape.

Can a QUIC connection survive a client switching networks?

Yes -- QUIC identifies a connection independently of the underlying IP address and port, so a connection can survive a client moving from WiFi to mobile data without being torn down and renegotiated from scratch.

Why can QUIC start sending encrypted data after just one round trip?

QUIC builds the TLS 1.3 handshake into connection setup itself, so a client and server exchange cryptographic and transport parameters together. For an already-known server, that can let encrypted application data flow after a single round trip (0-RTT) instead of a separate TCP handshake followed by a separate TLS handshake.

How does QUIC discover the largest packet size a network path supports?

QUIC uses DPLPMTUD (RFC 8899) to probe this directly at the transport layer, rather than relying on ICMP the way classic Path MTU Discovery does -- which keeps it working even when a network silently drops the ICMP messages PMTUD needs.