Jack Be Nimble, Jack Be QUIC

My router (Asus RT-AC68R) has a nice traffic monitor screen. I check it regularly. One day I noticed that the largest usage was attributed to QUIC.

QUIC has taken all the best qualities of TCP connections and TLS encryption and implemented it on UDP.

What is QUIC?

Simple. QUIC stands for Quick UDP Internet Connection.

Yeah, right.

There’s a good explanation here. If that article is too simple for you, try this one.

QUIC has taken all the best qualities of TCP connections and TLS encryption and implemented it on UDP.

Here’s why:

1. Reduced connection times. To establish TLS encryption, the client and the server need to perform a TLS handshake and exchange encryption keys. QUIC replaces this with a single handshake.
2. Better performance when data packets are lost. The QUIC protocol allows streams of data to reach their destination independently. They no longer need to wait for the missing data packet to be repaired.
3. Stable connections when networks are changed. If you are connected to a web server via TCP and your network suddenly changes, QUIC allows for a smoother transition by giving each connection to a web server a unique identifier. These can be reestablished by simply sending a packet rather than establishing a new connection, even if your IP changes.
4. Easier to improve and develop. QUIC can be implemented on the application level, making it a more flexible protocol.

But you’ll never see any of this. All you’ll see is faster.

So, who uses QUIC?

Google Chrome when it connects to Google servers. This includes all of Google’s services, i.e. YouTube, Blogger, Hangouts, etc.

Originally published at https://blog.benmoore.info.

IT professional, Formula 1 fan

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store