Fundamentals 17 min read

Understanding QUIC: Transport‑Layer Implementation of HTTP/3 and Its Key Features

QUIC, a UDP‑based transport protocol that merges TCP reliability, UDP speed, and TLS security, underpins HTTP/3 by eliminating TCP’s three‑way handshake and head‑of‑line blocking, offering connection migration, 0‑RTT latency, customizable congestion control, fully encrypted packets, and is already being deployed in services such as Tencent Cloud CDN.

Tencent Cloud Developer
Tencent Cloud Developer
Tencent Cloud Developer
Understanding QUIC: Transport‑Layer Implementation of HTTP/3 and Its Key Features

QUIC (Quick UDP Internet Connection) is a transport‑layer protocol introduced by Google that serves as the implementation foundation for HTTP/3. By leveraging UDP, QUIC overcomes many limitations of TCP‑based HTTP, especially in weak‑network environments, and improves overall communication experience.

1. What is QUIC? QUIC combines the reliability of TCP, the speed of UDP, and the security of TLS. It provides TCP‑plus‑HTTPS‑plus‑HTTP/2 functionality while reducing round‑trip latency because UDP eliminates the need for TCP’s three‑way handshake and slow‑start mechanisms.

2. Evolution of HTTP The article outlines the historical progression of HTTP (0.9 → 1.0 → 1.1 → 2.0 → 3.0) and explains why HTTP/3 adopts QUIC to solve the head‑of‑line blocking and congestion issues inherent in TCP‑based protocols.

3. Key QUIC Features

• Connection Migration : QUIC identifies a connection by a 64‑bit random Connection ID rather than the IP/port tuple, allowing seamless migration when a client switches between Wi‑Fi and cellular networks.

• Low Connection Latency : QUIC merges the TLS handshake with connection establishment, enabling 0‑RTT data transmission after the first handshake and reducing the total RTT compared with TCP + TLS + HTTP/2.

• Customizable Congestion Control : Congestion control is implemented in the application layer, allowing algorithms such as BBR or CUBIC to be selected per service or even per connection.

• No Head‑of‑Line Blocking : QUIC uses packet numbers and stream offsets, enabling out‑of‑order delivery and independent retransmission of lost packets, thus eliminating the head‑of‑line blocking problem of TCP and HTTP/2.

4. Protocol Composition QUIC packets consist of Flags, Connection ID, Version, Packet Number, Stream ID, Offset, and encrypted payload. All packet headers are authenticated, and the body is encrypted, providing strong security guarantees.

5. Security and Deployment The article notes that QUIC’s authenticated headers and encrypted bodies protect against tampering. Tencent Cloud CDN has integrated QUIC support and is currently in internal testing.

6. References A list of publicly available articles and technical blogs is provided for further reading.

QUICHTTP/3network performancecongestion controlConnection MigrationTransport ProtocolUDP
Tencent Cloud Developer
Written by

Tencent Cloud Developer

Official Tencent Cloud community account that brings together developers, shares practical tech insights, and fosters an influential tech exchange community.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.