Google Inc. about the transition from its own protocol version to the version being developed in the IETF specification. The variant of QUIC used in Chrome by Google differs in some details from the one in . Chrome supports both versions of the protocol, but by default, it still uses its own variant of QUIC.
As of today, 25% of users on the stable branch of Chrome have switched to using IETF QUIC, and this share will soon increase. According to Google statistics, compared to HTTP over TCP+TLS 1.3, the IETF QUIC protocol showed a 2% reduction in latency when searching in Google Search and a 9% decrease in rebuffering time on YouTube with an increase in bandwidth of 3% for desktop and 7% for mobile systems.
HTTP/3 the use of the QUIC protocol as a transport for HTTP/2. The QUIC (Quick UDP Internet Connections) protocol has been developed by Google since 2013 as an alternative to the TCP+TLS stack for the Web, addressing issues with long connection setup times and negotiation in TCP while eliminating delays due to packet loss during data transmission. QUIC is a layer on top of the UDP protocol, supporting multiplexing of multiple connections and providing encryption methods equivalent to TLS/SSL. Changes made to the protocol during standardization in the IETF led to the emergence of two parallel branches, one for HTTP/3 and the other supported by Google.
Source: opennet.ru
