Protocol ExplorerGuidesPricing

QUIC Protocol: Streams, TLS and Connection Migration

QUIC is a secure transport protocol carried in UDP datagrams. It combines transport setup with TLS and provides multiple independently ordered streams within one connection.

Updated · Editorial approach and simulation limits

QUIC combines transport setup with TLS

QUIC uses TLS 1.3 handshake messages to establish keys and authenticate the peer, while QUIC itself defines connection identifiers, streams, acknowledgments, loss detection and congestion control. A network capture therefore does not show a TCP handshake before an HTTP/3 exchange.

QUIC runs over UDP so user-space implementations can evolve transport behavior without changing the kernel TCP implementation. UDP is only the carrier: QUIC adds the reliability, security and stream functions that an application expects from a transport.

Streams isolate ordering between data flows

A QUIC connection can carry multiple streams. Bytes within a stream are delivered in order, while a loss affecting one stream does not automatically prevent delivery of data on an unrelated stream. Streams still share connection-level congestion control and path capacity.

This reduces one form of cross-stream head-of-line blocking compared with a single TCP byte stream, but it does not make QUIC immune to congestion or loss. An application can still be delayed by a slow stream, server processing or a constrained network path.

Connection IDs support path changes

QUIC connection IDs help endpoints identify a connection even when a network path changes an address or port. Before using a new path, endpoints validate it according to QUIC’s rules. This can help a connection survive a transition between networks, but migration is subject to peer policy and implementation support.

The transport also supports 0-RTT data in suitable resumed connections. Early data can be replayed, so applications and servers must apply the protocol’s replay considerations; it is not safe for every operation.

Read QUIC and HTTP/3 traces at the right layer

HTTP/3 maps HTTP semantics onto QUIC streams. A packet capture can expose UDP endpoints and some QUIC metadata, but most packet contents are protected. Use endpoint logs or authorized key material to inspect stream data; do not infer an HTTP status from an encrypted datagram.

Compare the dedicated QUIC lesson with the TCP handshake page to see which setup steps differ. RFC 9000 defines transport behavior, while RFC 9001 specifies using TLS with QUIC and RFC 9114 defines HTTP/3.

Explore QUIC interactively

Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.

Open the QUIC animation · Compare Free and Pro

Specification and source

For exact protocol requirements, consult the primary document: RFC 9000: QUIC — A UDP-Based Multiplexed and Secure Transport. This page summarizes selected behavior and is not a substitute for the specification.

Related protocol lessons

Browse all transport protocols · Compare QUIC and TCP connection behavior