I'm Feeling Lucky

10 Facts About QUIC

1.

QUIC is a general-purpose transport layer network protocol initially designed by Jim Roskind at Google, implemented, and deployed in 2012, announced publicly in 2013 as experimentation broadened, and described at an IETF meeting.

FactSnippet No. 1,567,883
2.

QUIC is used by more than half of all connections from the Chrome web browser to Google's servers.

FactSnippet No. 1,567,884
3.

QUIC improves performance of connection-oriented web applications that are currently using TCP.

FactSnippet No. 1,567,885
4.

QUIC aims to be nearly equivalent to a TCP connection but with much-reduced latency.

FactSnippet No. 1,567,886
5.

QUIC includes a number of other more mundane changes that improve overall latency and throughput.

FactSnippet No. 1,567,887

Related searches

Google IETF Chromium HTTP Google Chrome
6.

QUIC can be implemented in the application-space, as opposed to being in the operating system kernel.

FactSnippet No. 1,567,888
7.

Protocol that was created by Google and taken to the IETF under the name QUIC is quite different from the QUIC that has continued to evolve and be refined within the IETF.

FactSnippet No. 1,567,889
8.

The original Google QUIC was designed to be a general purpose protocol, though it was initially deployed as a protocol to support HTTP in Chromium.

FactSnippet No. 1,567,890
9.

The current evolution of the IETF QUIC protocol is a general purpose transport protocol.

FactSnippet No. 1,567,891
10.

QUIC code was experimentally developed in Google Chrome starting in 2012, and was announced as part of Chromium version 29.

FactSnippet No. 1,567,892