Skip to end of metadata
Go to start of metadata

An experimental protocol developed by Google to speed up latency-sensitive applications such as Web search. A prime goal is that connections can be established more quickly than with TCP ("zero RTT connection establishment"). The protocol is layered on top of UDP for deployability. According to a Chromium Blog article from April 2015, "roughly half of all requests from Chrome to Google servers are served over QUIC".

The IETF QUIC Working Group was chartered in October 2016, with the following goals stated in its original charter:

  • Minimizing connection establishment and overall transport latency or applications, starting with HTTP/2;
  • Providing multiplexing without head-of-line blocking;
  • Requiring only changes to path endpoints to enable deployment;
  • Enabling multipath and forward error correction extensions; and
  • Providing always-secure transport, using TLS 1.3 by default.

References

– SimonLeinen - 2017-09-27 - 2018-11-05

  • No labels