Google company about the beginning of the replacement of its own version of the protocol to the version developed in the IETF specification. Google's version of QUIC used in Chrome differs in some details from the version from . At the same time, Chrome supports both protocol options, but still used its QUIC version by default.
Starting today, 25% of Chrome stable users have switched to IETF QUIC, and this proportion will be increased in the near future. Compared to HTTP over TCP+TLS 1.3, the IETF QUIC protocol showed a 2% reduction in Google Search latency and a 9% reduction in YouTube rebuffering time, while increasing throughput by 3% for desktop and 7% for mobile, according to Google statistics. systems.
HTTP / 3 using the QUIC protocol as a transport for HTTP/2. The QUIC protocol (Quick UDP Internet Connections) has been developed by Google since 2013 as an alternative to TCP + TLS for the Web, solving problems with long setup and negotiation times for connections in TCP and eliminating delays in case of packet loss during data transfer. QUIC is an add-on to the UDP protocol that supports multiplexing of multiple connections and provides encryption methods equivalent to TLS/SSL. During the standardization process in the IETF, changes were made to the protocol, which led to the emergence of two parallel existing branches, one for HTTP / 3, and the second supported by Google.
Source: opennet.ru