Skip to content
The QUIC Transport Protocol: Design and Internet-Scale Deployment 4 min

Adam Langley, Alistair Riddoch, Alyssa Wilk, Antonio Vicente, Charles Krasic, Dan Zhang, Fan Yang, Fedor Kouranov, Ian Swett, Janardhan Iyengar · SIGCOMM 2017

The QUIC Transport Protocol: Design and Internet-Scale Deployment

The protocol behind HTTP/3: faster handshakes, streams that do not block each other, and connections that survive changing networks. Count round trips and lose a packet.

Read the original paper

Networking · Yellow Belt · Pro · 4 min read

The QUIC Transport Protocol: Design and Internet-Scale Deployment

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.

QUIC merges security and reliability into one layer built on UDP, so it can combine their handshakes and give each request its own stream.

Keep reading with Pro

This paper is part of Pro. Pro and Architect open the full breakdown, with animated diagrams, interactive elements you can play with and a quiz. A few papers stay free to read in full.

Still to read

3 more sections, 1 more diagram and 3 interactive elements to play with

  • Faster handshakes
  • No more head-of-line blocking
  • Surviving a change of network

Found this breakdown useful?

Share it with someone else wrestling with this paper.

Discussion0

Join the Discussion

Sign in to leave comments, reply to others, or like insights.

Sign In to ScaleDojo

No comments yet. Be the first to start the thread!

Enjoyed this? Get more like it.

New paper breakdowns, levels, and one concept worth knowing, straight to your inbox.

No spam, ever. Unsubscribe in one click.

Enjoyed this content?

Your support keeps us creating free resources

We put a lot of hours into researching and writing these guides. If it helped you, consider buying us a coffee. Every bit goes toward keeping ScaleDojo's content free and growing.

$

One-time payment via Stripe. ScaleDojo account required.