QUIC
Definition
A modern transport protocol built on UDP that combines connection establishment, encryption negotiation, and reliable data delivery into a single handshake, reducing connection setup latency and improving performance over lossy or high-latency network paths.
Key Points
- Combines what conventional TCP and TLS handle as separate sequential handshakes into a single, faster combined handshake, directly reducing the round trips needed before data can start flowing
- Built on top of UDP rather than TCP, giving QUIC implementation flexibility that operating directly at the TCP layer wouldn't provide, while still delivering the reliable, ordered data delivery TCP is known for
- Encrypts nearly all of its protocol metadata by default, in contrast to TCP's traditionally separate and optional TLS encryption layer, providing security benefits beyond what conventional TCP connections offer without additional configuration
- Handles connection migration better than TCP, maintaining an active connection through network changes — switching between Wi-Fi and cellular, for example — that would typically require TCP to reestablish its connection from scratch
- Serves as the transport foundation for HTTP/3, reflecting the web platform's shift toward QUIC's faster connection setup and improved lossy-network performance relative to the TCP-based transport HTTP/2 and earlier versions relied on
Concept
Where a conventional TCP connection secured with TLS requires separate sequential handshakes — first establishing the TCP connection, then separately negotiating TLS encryption — QUIC combines both steps into a single combined handshake, reducing the round trips needed before application data can begin flowing, while still providing the reliable, ordered delivery TCP guarantees and the encryption TLS provides, now built into QUIC's core design rather than layered on as a separate step.
Explainer
The latency reduction QUIC's combined handshake delivers matters disproportionately on exactly the connections where round-trip time is highest — a high-latency or lossy network path benefits far more from eliminating an extra handshake round trip than a fast, reliable local connection would, which is precisely why QUIC's performance advantage is most pronounced for mobile, satellite, or otherwise challenging network paths rather than being a uniform improvement across all connection types. This is also why QUIC's connection migration capability matters specifically for mobile use cases: a TCP connection tied to a specific network path breaks and must reestablish when the underlying network changes, while QUIC can maintain session continuity through exactly that kind of network transition, directly benefiting mobile users moving between Wi-Fi and cellular connectivity. For CE verticals, QUIC's performance benefits are most relevant to latency-sensitive or mobile-heavy application traffic — field operations applications accessed over cellular or satellite connectivity, and any web-based application increasingly served over HTTP/3, both benefit from QUIC's reduced connection setup latency relative to conventional TCP-based alternatives.
Cite this entry
QUIC. ConnectedEarth Knowledge Base. https://connectedearth.space/knowledge-base/quic/ (updated 13 September 2026).