Transport Protocols: TCP, UDP and QUIC
Transport protocols carry application data between endpoints. Their setup, ordering, recovery and security properties are different, so identify the transport before diagnosing an application exchange.
Curated learning paths from Protocol Explorer · Editorial approach and simulation limits
TCP, UDP and QUIC occupy related roles but expose different contracts to applications. These concise lessons focus on connection setup, delivery semantics and the clues available in a packet capture.
Choose transport by delivery and stream behavior
Transport protocols describe how endpoints exchange data above IP. TCP provides a reliable, ordered byte stream, so applications need framing and may wait for missing bytes before delivering later data to the same stream. UDP preserves datagram boundaries but leaves delivery, ordering and congestion behavior to the application or another layer. QUIC runs over UDP while implementing encrypted connections and independent streams, so it is not simply “UDP with a new port.”
Begin with the exchange the capture actually shows. Use TCP when you need to reason about SYN setup, sequence numbers, acknowledgments, retransmission and connection close. Use UDP when the message boundaries and application retry rules matter more than a transport connection. Learn QUIC after those basics, then follow its connection IDs, packet protection and per-stream behavior in a QUIC-aware trace. WebRTC can add ICE path checks and media-specific transport behavior.
Choose a protocol based on the application’s latency, ordering, reliability and deployment requirements, not on a single port number. A completed TCP handshake does not prove an HTTP request succeeded, and a UDP packet leaving a host does not prove the receiver processed it. Keep IP delivery, transport state and application response as separate checkpoints.
Explore protocols in this topic
- TCP
A reliable ordered byte stream with sequence numbers, acknowledgments and retransmission.
- UDP
Independent datagrams with ports and checksums but no built-in delivery recovery.
- QUIC
A secure transport over UDP with streams, loss recovery and connection identifiers.
Choose the transport model before reading payloads
TCP acknowledgments track byte sequence space; UDP preserves datagram boundaries without promising delivery; QUIC adds secure streams and recovery above UDP. Seeing UDP in a capture does not tell you whether the application is QUIC, DNS, NTP or another protocol.
A connection is more than a successful setup
A completed handshake establishes transport state. It does not prove that a later TLS certificate was accepted, an HTTP request succeeded or an application processed the bytes. Follow the exchange through the first relevant application response.
Compare protocols in a worked example
The QUIC vs TCP guide compares setup, streams, loss and HTTP versions. For the next layer, see the application protocol hub.