QUIC vs TCP: Setup, Streams and HTTP/3
TCP and QUIC both carry application data reliably, but they expose different connection and stream models. QUIC runs over UDP and integrates TLS; TCP provides an ordered byte stream that applications can secure separately.
By Protocol Explorer · Updated
Start with the transport each application actually uses
TCP is an IP transport with a connection state machine and one ordered byte stream in each direction. HTTP/2 commonly uses TCP with TLS. QUIC is a secure transport carried in UDP datagrams; HTTP/3 maps HTTP semantics onto QUIC streams.
This means a capture for HTTP/3 will not begin with a TCP SYN. The UDP header is only the outer carrier for QUIC’s own connection IDs, packets, acknowledgments, loss recovery and stream frames.
Connection setup and encryption are arranged differently
A typical TCP active open uses SYN, SYN-ACK and ACK to synchronize sequence numbers. When HTTPS uses TCP, TLS negotiation follows that transport setup before protected HTTP data is sent.
QUIC integrates the TLS 1.3 handshake into its transport setup. The TLS handshake provides authentication and key establishment while QUIC establishes its transport parameters. The exact timing depends on handshake state and resumption; comparing only the number of visible packets misses processing, round-trip time and path conditions.
One TCP stream and multiple QUIC streams handle ordering differently
TCP presents one ordered byte stream. If earlier bytes are missing, later bytes in that same stream cannot be delivered to the application until the gap is recovered. This is head-of-line blocking within the connection’s stream.
QUIC supports multiple independently ordered streams. Loss affecting data on one stream does not necessarily block delivery on another stream, although all streams still share connection-level congestion control and network capacity. QUIC reduces one form of cross-stream blocking; it does not remove delay caused by congestion or a slow peer.
Loss recovery exists in both protocols
TCP uses acknowledgments, retransmission and congestion control to deliver an ordered stream. QUIC defines packet acknowledgments, loss detection and congestion control at the QUIC layer. UDP itself supplies none of those functions.
A packet capture may show repeated TCP sequence ranges or QUIC packet-number and acknowledgment behavior, but encryption hides much of QUIC’s contents. Use endpoint telemetry or authorized key logs for detailed HTTP/3 analysis. Do not compare raw TCP and UDP packet counts as though each packet represented the same useful application work. QUIC packet protection, header behavior, acknowledgment patterns, coalescing and path MTU affect observed sizes; application timing is a more useful measure than a single segment count.
Connection migration is a QUIC feature with conditions
QUIC connection IDs can help endpoints associate packets with a connection when an address or port changes. Endpoints validate a new path and follow the migration rules in RFC 9000. This can help a session survive a change of network, but it is not a guarantee that every application or server permits migration.
TCP connections are bound to their endpoint tuple. If the address or port changes, the usual TCP connection cannot simply continue as the same transport connection; the application normally establishes a new one.
HTTP/2 and HTTP/3 keep semantics while changing the transport
HTTP/2 commonly multiplexes streams over one TCP connection. A lost TCP segment can delay delivery of later bytes in that connection, even if they belong to a different HTTP/2 stream. HTTP/3 uses QUIC streams so transport-level ordering is scoped differently.
The HTTP methods, status codes and resource semantics remain part of HTTP. A different transport does not change whether a server returned 404 or whether an application accepted a request.
0-RTT has replay considerations
QUIC can send early data in a resumed connection under conditions defined by the TLS and QUIC specifications. Early data may be replayed, so applications and servers should avoid using it for operations whose repeated execution would be unsafe.
0-RTT is not available as a shortcut for every new connection. A trace or performance comparison should state whether the session resumed, whether early data was accepted and how the application handled replay-sensitive requests.
How to compare traces without overclaiming
For TCP, follow the SYN sequence, negotiated options, byte ranges and cumulative acknowledgments. For QUIC, begin with the UDP endpoints, connection IDs, handshake state and packet timing; use authorized endpoint data for encrypted frames. Then compare when the first useful application response arrived.
Protocol Explorer’s diagrams are scripted examples with illustrative times. They teach the relationship between messages, not a benchmark proving that one protocol is always faster. Network path, server implementation, connection reuse, loss and workload all affect results.