Why QUIC and HTTP/3 Are Transforming Mobile Network Performance

On June 7, 2022, the IETF officially released the HTTP/3 standard (RFC 9114), completing the six core QUIC specifications and ushering in a new era of network protocols.

Since 2018, Alibaba's Mobile Taobao has been experimenting with QUIC and, by 2021‑22, achieved large‑scale deployment of IETF‑compliant QUIC and HTTP/3, reducing core transaction latency by 15‑20% and open‑sourcing the XQUIC protocol library.

When is QUIC the right TCP replacement? It excels on public‑internet links with long round‑trip times, high packet loss, and wireless variability, while TCP/DCTCP remains suitable for controlled data‑center environments.

The key architectural shift of QUIC is moving the transport layer from kernel to user space, enabling tight integration with application logic and opening new possibilities for custom transport behavior, similar to WebRTC's success in audio‑video streaming.

Four stages of technology adoption are described: (1) using the technology to gain immediate business value, (2) deepening understanding of underlying principles, (3) building in‑house capabilities, and (4) leading the industry through open‑source or standards contributions.

Applying QUIC/HTTP3 improves performance by eliminating TCP head‑of‑line blocking, supporting multiplexed streams, and offering 0‑RTT handshakes. QUIC provides both reliable Stream transport and unreliable Datagram transport for real‑time media.

TCP suffers from head‑of‑line blocking because packets must be delivered in order, which multiplexed streams cannot fully resolve.

QUIC also introduces faster loss detection (packet‑number thresholds and timer‑based timeouts) and precise RTT measurement, enhancing congestion control.

To use these innovations, XQUIC implements the full QUIC and HTTP/3 stack, passes IETF interoperability tests, and is available at https://github.com/alibaba/xquic with documentation and RFC translations.

Server‑side UDP performance challenges are addressed by combining eBPF XDP packet hijacking with the ExpressUDP library, achieving over 26% higher protocol‑stack throughput compared to the Linux kernel default.

Integrating ExpressUDP, Tengine, and XQUIC provides a high‑performance, zero‑copy UDP solution that will be open‑sourced for the community.

In conclusion, the authors encourage developers to embrace deep technical exploration, contribute to open‑source, and respect the long‑term health of the technology ecosystem.

References:

RFC 9114 – HTTP/3: https://datatracker.ietf.org/doc/rfc9114/

RFC 9204 – QPACK: https://datatracker.ietf.org/doc/rfc9204/

Interoperability test: https://interop.seemann.io/

XQUIC repository: https://github.com/alibaba/xquic

XDP paper: https://dl.acm.org/doi/pdf/10.1145/3281411.3281443

ExpressUDP: https://gitee.com/anolis/ExpressUDP

Multipath extension draft: https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/