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:

The combination of QUIC and HTTP/2 with some enhancements should result in a new "HTTP/3" standard.

QUIC Encryption vs. Performance Analysis

QUIC mandates encryption for most information, including traditional "transport-level" fields such as sequence numbers. This complicates some performance analysis approaches. Various tools (e.g. qlog/qvis) and (protocol) mechanisms (such as the "spin" bit) have been suggested to address this.


 (References

– SimonLeinen - 2017-09-27 - 2020-07-23