UDP provides minimal datagram transport: it adds ports and a checksum but does not establish a reliable ordered byte stream. QUIC builds richer transport behavior in user space on top of UDP, including encrypted transport, streams, connection migration and modern loss/congestion mechanisms. HTTP/3 maps HTTP semantics onto QUIC streams.
Remember the shape, not the sentence
“UDP is a blank road. QUIC builds a modern transport system on top of that road instead of modifying the traditional TCP stack.”
What UDP does
UDP is connectionless and message-oriented. Applications choose whether and how to handle reliability, ordering, retransmission and pacing.
What QUIC adds
QUIC provides reliable streams, TLS 1.3 integration, congestion control, connection IDs and independent stream delivery on top of UDP datagrams.
Why independent streams matter
Loss on one QUIC stream does not require unrelated streams to wait for the same TCP byte-stream order. This reduces a transport-level source of head-of-line blocking.
See the mechanism before you memorize it
One diagram, one causal story, one reconstruction task.
UDP & QUIC: why HTTP/3 ditched TCP — causal map
UDP
Minimal datagram service between endpoints.
QUIC
Adds encrypted transport semantics and multiplexed streams.
HTTP/3
Maps HTTP requests/responses onto QUIC streams.
Loss
QUIC retransmits data at the stream/packet framing level rather than retransmitting a TCP byte stream.
Draw the idea yourself
Rebuild the core flow on a real canvas before moving to the worked walkthrough.
Walk the system
UDP
Minimal datagram service between endpoints.
QUIC
Adds encrypted transport semantics and multiplexed streams.
HTTP/3
Maps HTTP requests/responses onto QUIC streams.
Loss
QUIC retransmits data at the stream/packet framing level rather than retransmitting a TCP byte stream.
Migration
Connection IDs help a QUIC connection survive some network-path changes.
Stack comparison
The point is not 'UDP is faster'. UDP is merely the substrate; QUIC supplies the sophisticated transport behavior that HTTP/3 needs.
HTTP/1.1, HTTP/2 → TCP → IP
HTTP/3 → QUIC → UDP → IP
QUIC = streams + TLS 1.3 + congestion control + connection IDsWhat usually goes wrong
Close the tab. Rebuild it from memory.
Read the question, answer aloud, then reveal.
Why use UDP under QUIC?Reveal answer
UDP provides a broadly deployable datagram substrate while allowing QUIC to implement its transport features in user space.
What is a QUIC stream?Reveal answer
An independently managed ordered byte sequence within a QUIC connection, allowing multiple transfers to progress concurrently.
Does QUIC remove all ordering?Reveal answer
No. Each stream is ordered; the important difference is that unrelated streams do not share one global byte sequence.
Make this idea travel.
Connect it next to: http-versions • tcp-packet-analysis • dns.