Systems and protocols · Intermediate

QUIC: streams and connections over UDP

Understand independent stream delivery, connection identity and the limits that remain on a shared path.

Ask Logeia about this articleTry the three questionsReview your answers

Updated

On this page
  1. What QUIC adds above UDP
  2. Separate stream delivery gaps
  3. Connection identity can outlive an address
  4. Encryption does not ensure reachability
  5. Ask Logeia about this articleCheck your understanding

What QUIC adds above UDP

QUIC uses UDP as its underlying datagram delivery mechanism while adding streams, multiplexing, encryption and loss recovery. The absence of ordering in UDP does not mean that a QUIC stream is unordered. Stream data has positions that let the receiver reconstruct its ordered contents.

HTTP/3 is an application protocol using QUIC, not another name for QUIC itself. This layered view is useful when diagnosing a failure: the application exchange, QUIC connection and UDP path each provide different observations and impose different constraints.

Separate stream delivery gaps

If stream A has a missing byte range, an independent stream B need not wait for that gap to be repaired merely to deliver its own received data. This differs from placing several HTTP/2 streams over one ordered TCP byte stream.

The independence is not absolute isolation. Application dependencies can still make B wait for A, and streams share path capacity and connection-level congestion behavior. Avoid turning the narrower delivery property into the claim that a loss on one stream can never affect another operation’s performance.

Connection identity can outlive an address

Connection IDs allow a QUIC endpoint to identify a connection without relying exclusively on one fixed address-and-port tuple. That can support continuity when a mobile device changes its network path. The peer still needs procedures such as path validation before trusting traffic on a newly observed path.

Imagine moving from Wi-Fi to another access network while continuing one application conversation. Connection identity and the current delivery address are related but distinct concepts. This does not guarantee survival through every outage, server restart or unsupported migration scenario.

Encryption does not ensure reachability

QUIC integrates TLS 1.3 for key establishment and protection, but encrypted transport does not replace application authorization or duplicate-operation handling. Early data requires its own replay-aware application policy. Those concerns remain even when connection establishment is fast.

Some networks restrict UDP. A performance comparison must therefore control path conditions, loss and connection reuse rather than attributing every timing difference to the protocol label. Record whether QUIC was actually used and what fallback behavior occurred when the desired path was unavailable.

Reading and practice are recorded separately in this browser, for each language.

Learn this in order

Understand the systems behind the web · STEP 10

Choose a learning path