Open a web page over a mobile network and a surprising amount of time disappears before the first byte of the page arrives. The phone and server swap messages to set up the connection, swap more to agree on encryption, and only then does the request go out. Every swap costs one round trip across the network, and on a slow link a round trip can take a fifth of a second.
QUIC is Google's answer, described in a 2017 paper after several years of running it on real traffic. It replaces the old TCP plus TLS stack with one new protocol, built on top of UDP, that sets up secure connections faster, avoids a problem called head-of-line blocking, and can keep working when you move from Wi-Fi to cellular.
QUIC merges the transport and encryption handshakes, sends several independent streams over one connection, names the connection with an ID instead of an address, and runs in the application so it can be updated quickly. The paper estimates that 7 percent of Internet traffic was already QUIC.
Why not just improve TCP?
TCP is built into operating systems, and the boxes in the middle of the Internet (firewalls, load balancers, NATs) inspect and sometimes modify its packets. The paper says that deploying changes to TCP has become extremely hard, a problem often called protocol ossification. New TCP features take years to reach users, if they arrive at all.
QUIC dodges the problem. It uses UDP as a substrate, which the network passes along without opinions, and it encrypts almost everything, so middleboxes cannot meddle. It lives in the application rather than the kernel, so Google can ship a new version with a browser or server update.
