BT

Google Will Propose QUIC As IETF Standard

| by Sergio De Simone Follow 14 Followers on Apr 22, 2015. Estimated reading time: 1 minute |

Google has recently announced that they will propose their experimental transport layer network protocol QUIC as a IETF Standard. Furthermore. Google has provided the first available figures about the improvements in page load time that QUIC makes possible.

Since QUIC introduction in 2013, Google has been increasing the amount of traffic that Google services serve over QUIC. According to Google, “today, roughly half of all requests from Chrome to Google servers are served over QUIC,” and this will lead to making QUIC the “default transport from Google clients — both Chrome and mobile apps — to Google servers.”

Google also adds that their performance analysis at scale revealed that “QUIC provides a real performance improvement over TCP.” This is related to QUIC’s:

  • Lower-latency connection establishment, which benefits already established connections. In this case, Google has measured a 3% improvement in mean page load time with Google Search.
  • Improved congestion control and loss recovery, which is particularly relevant under poor network conditions. In this case, Google has measured a full second decrease in Google Search page load time “for the slowest 1% of connections,” and up to 30% fewer rebuffers when watching YouTube videos over QUIC.

QUIC is a protocol that Google created in an effort to reduce TCP web latency. QUIC is built on top of UDP, since, according to Google, “making significant changes to TCP is next to impossible” due to it being implemented in OS kernels and firmware.

A commenter on Hacker News pointed out that Google has succeeded in quietly moving “a large user base from open protocols to a proprietary protocol”, which is in itself a display of the power coming from controlling both hugely successful services and the dominant web browser, and that this might be worrying in case Google decided to delay the standardization process or not pursue it at all. Other commenters in the same thread pointed out that Google’s process about QUIC is open and that anyone can contribute to QUIC’s definition and development through its news group. Finally, it must be also noted that Chrome support for QUIC can be easily disabled by the end-user.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT