Facts about QUIC Protocol
- 10
The QUIC protocol is built on top of UDP rather than TCP, allowing it to implement custom reliability and flow control mechanisms without kernel modifications.
- 09
Approximately 7% of internet traffic utilized QUIC protocol by 2023, with major CDNs like Cloudflare and Akamai deploying it to improve video streaming and web performance.
- 08
Encryption in QUIC protects packet headers and payload together, whereas TCP leaves headers unencrypted, preventing middleboxes from inspecting or modifying connection metadata.
- 07
Initial packet sizes in QUIC are limited to 1200 bytes during the handshake to ensure compatibility with networks that have smaller MTUs and reduce amplification attack vulnerabilities.
- 06
QUIC's congestion control uses a pacer that spreads packet transmission over time to reduce burst losses, whereas TCP traditionally sends multiple segments immediately in response to ACKs.
- 05
Connection migration in QUIC allows clients to seamlessly switch between networks, such as from WiFi to cellular, while maintaining the same connection ID and session state without requiring a new handshake.
- 04
Packet loss in QUIC is detected through selective acknowledgments rather than TCP's cumulative approach, allowing senders to retransmit only lost packets without resending entire windows of data.
- 03
Zero-RTT connection resumption in QUIC allows clients to send application data immediately on reconnection without waiting for server acknowledgment, enabling faster session restoration than TLS 1.2.
- 02
Multiplexing multiple streams over a single QUIC connection eliminates head-of-line blocking that occurs in HTTP/2, allowing independent streams to progress without waiting for lost packets from other streams.
- 01
Google's QUIC protocol, standardized as RFC 9000 in 2021, reduces connection establishment latency to a single round trip compared to TCP's three-way handshake.