"The standard way to do secure web browsing involves communicating over TCP + TLS, which requires 2 to 3 round trips with a server to establish a secure connection before the browser can request the actual web page," Google's Chrome team wrote in a blog post.
"QUIC is designed so that if a client has talked to a given server before, it can start sending data without any round trips, which makes web pages load faster."
- Packet pacing to reduce packet loss
- A pluggable congestion control mechanism
- UDP transport to avoid TCP head-of-line blocking
- High security similar to Transport Layer Service (TLS)
- Packet error correction to reduce retransmission latency
- A connection identifier to reduce reconnections for mobile clients
- Fast (0-RTT) connectivity similar to TLS Snapstart combined with TCP Fast Open.
"Today, roughly half of all requests from Chrome to Google servers are served over QUIC and we're continuing to ramp up QUIC traffic, eventually making it the default transport from Google clients — both Chrome and mobile apps — to Google servers," Chrome team explained.