We’re looking at the latest state of the QUIC and HTTP / 3 protocols, which will likely speed up the internet in 2021.
A reliable and secure transmission protocol that reduces latency QUIC (Quick UDP Internet Connections) resulting from manipulating the HTTP logic on the QUIC. HTTP / 3 (Hypertext Transfer Protocol / 3), protocols developed and distributed together. In this article, we will talk about the current status of protocols, their distribution on the web, and how technologies will develop in the near future.
The QUIC and HTTP / 3 protocols have reached another important milestone, with a short time to completion. Most adaptations are now interoperable, while servers are also receiving updates to support QUIC and HTTP / 3 protocols and are ready for these protocols.
QUIC and HTTP / 3 in IETF
QUIC and HTTP / 3, In the IETF (Internet Engineering Task Force) As we continue to develop through a collaborative and iterative standardization process, we have now reached an important point. Just a few weeks ago (after four years, 22 face-to-face meetings, 1,800 releases, and thousands of bug reports), the working group concluded its last meeting for topics. In other words, the heads of the working group requested the final design examples of the protocols from the working group.
In summary, the QUIC working group is finally completing the development of its new protocols.
This is a big deal, because five years after HTTP / 2 was published, it was the main transport protocol that QUIC was trying to replace. Of TCP (Transmission Control Protocol) Almost forty years have passed since it was completed and presented.
IETF specifications as shown in the figure below IETF Requests for Comments (RFCs) still more before publishing a few important steps remained. On the other hand, most of the time in this process is spent in the evolution phase, which results in the working group’s final call to get a rough consensus on specifications. This is the stage that is currently being completed. At this point, any new problem raised against the design of protocols – even the minor ones – must go through additional process layers and have urgency and importance before being addressed by the working group to change specifications.
Fastly Engineer Jana Iyengar, author of the original article, states that the company loves the new protocol and that many employees within the company have been involved in developing the protocol specifications from the beginning. Fastly creates its own applications of these protocols, sets them up and makes them available to its customers. Investing deeply in making these technologies a success, the firm believes the new protocol is compatible with what they want to build: a faster, more resilient, and more reliable internet.
“As we conduct this study and are excited about the advancement of this rapidly changing technology, we understand that it is difficult to monitor the situation from outside. This post will clarify the state of the QUIC and HTTP / 3 development in IETF and their deployments around the world, and lay out our best guess of what to expect in the near future. ”
Changing an internet protocol, specifically a transport protocol designed to replace TCP for the web, requires that all communicating entities be able to talk to each other without any problems. The Internet is basically a multi-provider ecosystem and as a result communication almost always involves multiple adaptations of the same protocol. In order to be successfully deployed, various vendors must create QUIC applications and these applications must work with each other.
Vendors including Apple, Google, Microsoft, Mozilla and Fastly are working on their own apps, many of which are now fairly mature. These practitioners meet periodically to test their applications against each other, and many also participate in an automated interop test tool called QUIC Interop Runner, which is running continuously. Interop Runner shows the current state of HTTP / 3 and QUIC interoperability between participating applications over a series of accuracy and performance tests.
The community of practitioners working on these protocols has learned that open and continuous communication with each other is necessary to implement and distribute these protocols. These practitioners have been in close contact with each other as the protocol has evolved in recent years, and excitingly, most applications are close to being fully interoperable with each other.
- Google Chromesupports HTTP / 3 draft version h3-29 on all channels. Google has turned on HTTP / 3 for a small percentage of Chrome users on all channels. Users can also manually enable the draft version of h3-29 on any Chrome channel. (This is different from support for GQUIC, the older, proprietary protocol built by Google that is still used by the majority of Chrome users primarily for Google servers. Chrome is expected to replace GQUIC with HTTP / 3 and QUIC. Chrome is expected to replace HTTP / 3 and GQUIC distribution will decrease as QUIC distribution increases.)
- Microsoft EdgeIt uses Chrome’s networking stack, which includes QUIC and HTTP / 3 implementations, and thus follows Chrome closely while supporting these protocols. Edge has these protocols enabled by default for a small portion of Dev and Canary users running the draft version of h3-29. Users can manually open the draft version of h3-29 on any Edge channel.
- Mozilla Firefoxsupports HTTP / 3 draft version h3-29 in nightly structure which can be manually enabled.
- Apple Safarisupports HTTP / 3 draft version h3-29 as an experimental feature that can be manually enabled.
- Apple It includes support for HTTP / 3 draft version h3-29 as an experimental feature that can be manually enabled for apps on iOS and macOS, iOS 14 and macOS Big Sur.
- Microsoft Windows has its own implementation of HTTP / 3 and QUIC used by the IIS web server and is being tested for internal online services such as M365. This app supports draft versions h3-27, h3-28 and h3-29.
- Google’s There is no general plan for HTTP / 3 and QUIC availability and support on the Android platform. But Chrome runs on Android, and Android apps (and a few) can use Chrome’s network stack (cronet), which includes QUIC and HTTP / 3 apps.
A modern network is on the horizon
So where are all these developments taking us in terms of the ultimate QUIC and HTTP / 3 distribution in the world? To make a few guesses; Looking at the environment, this year we will see the rapidly increasing QUIC and HTTP / 3 support by clients, as well as higher volume tests on pre-release channels first, followed by clients that enable QUIC and HTTP / 3 in their stable versions.
Companies like Fastly and Cloudflare are excited to see these protocols on the other side of the finish line. The teams will participate in the final stages of the IETF process and closely monitor various distributions. We will keep you updated as these protocols are implemented and provide a better web experience worldwide.