IETF (Internet Engineering Task Force) announced the HTTP/3 standards, a document has appeared on the RFC Editor, numbered RFC 9114, the current status is “PROPOSED STANDARD”, but has not yet become an official standard.
JOIN US ON TELEGRAM
The Internet Engineering Task Force (IETF) first started HTTP/2 in 2015, and one of the major improvements it brought was support for reuse. But it uses TCP as the transport protocol and the loss recovery mechanism in TCP, so lost packets still cause delays for all active transactions.
HTTP/3 adopts the UDP-based QUIC protocol that Google has explored for many years, formerly known as HTTP-over-QUIC, and was approved by the IETF in 2018 to be renamed HTTP/3.
Moreover, HTTP /3 can further improve the transfer process, as lost packets only affect the activities directly affected by it. In the case of the same packet loss rate, the request time of HTTP/3 is significantly lower than that of HTTP/2.
The documentation page shows: The QUIC transport protocol has several features required for HTTP transport, such as stream multiplexing, per-stream flow control, and low-latency connection establishment.
This document describes the mapping of HTTP semantics on QUIC. This document also identifies the HTTP/2 features that QUIC includes, and describes how to port HTTP/2 extensions to HTTP/3.
Although it has not yet become an official standard, HTTP/3 has been supported by most mainstream browsers, including Google Chrome, and Firefox.
