HTTP-over-QUIC becomes the HTTP/3 protocol

The HTTP-over-QUIC protocol is officially known as HTTP/3. The development of the QUIC transport protocol began with Google, initially as an HTTP-over-UDP use case, which later evolved into the HTTP/2-encrypted-over-UDP protocol. When the IETF started to standardize QUIC, it was divided into two layers: transport and HTTP.

The transport protocol can be used to transport other data, not limited to HTTP or HTTP-like protocols, but the name still uses QUIC.

“When the work took off in the IETF to standardize the protocol, it was split up in two layers: the transport and the HTTP parts. The idea being that this transport protocol can be used to transfer other data too and its not just done explicitly for HTTP or HTTP-like protocols. But the name was still QUIC.

People in the community has referred to these different versions of the protocol using informal names such as iQUIC and gQUIC to separate the QUIC protocols from IETF and Google (since they differed quite a lot in the details). The protocol that sends HTTP over “iQUIC” was called “hq” (HTTP-over-QUIC) for a long time.”

Developers say Facebook has completed interoperability between the two HTTP/3 implementations. HTTP 1.1 was released in 1999 and HTTP/2 was in 2015.