Getting to grips with quiche, Cloudflare's QUIC and HTTP/3 library.Ī review of SIGCOMM's EPIQ workshop on evolving QUIC. Understanding protocol performance using WebPageTest. The roles of Server Push and Prioritization in HTTP/2 and HTTP/3. QUIC & HTTP/3 packet capture and analysis using Wireshark. QUIC & HTTP/3 logging and analysis using qlog and qvis. The table below gives an overview of the episodes that are available on demand.
I've also been lucky to have some guest experts join me along the way. There are over 12 hours of content including the basics of QUIC, ways to measure and debug the protocol in action using tools like Wireshark, and several deep dives into specific topics.
If you're more of an interactive visual learner, you might be pleased to hear that I've also been hosting a series on Cloudflare TV called "Levelling up Web Performance with HTTP/3".
We've collected a bunch of resource links at. And in a while, once Last Call completes and the RFCs ship, you'll start to see websites simply offer Alt-Svc: h3="… (note, no draft version!). So today, if you visit a website with HTTP/3 enabled-such as -you’ll probably see response headers that contain Alt-Svc: h3-29="…. For the average person in the street, there's not really much difference between 29 and 32. This shouldn't be surprising, as foundational aspects crystallize the scope of changes between iterations decreases. Although draft 32 is the latest specification, the community has for the time being settled on draft 29 as a solid basis for interoperability. HTTP/3 has been generally available on the Cloudflare edge since September 2019, and we've been delighted to see support roll out in user agents such as Chrome, Firefox, Safari, curl and so on. The QUIC specification has been mature and deployable for a long time now. At the end of the Last Call period, the stakeholders will take stock, address feedback as needed and, fingers crossed, go onto the next step of requesting the documents be published as RFCs on the Standards Track.Īlthough specification and implementation work hand in hand, they often progress at different rates, and that is totally fine. Now is the time to solicit feedback from the wider IETF community for review. IETF Last Call marks the point that the group and their responsible Area Director (in this case Magnus Westerlund) believe the job is almost done. These aspects operate hand in hand, helping the Working Group move towards satisfying the goals listed in its charter. Then, there's implementing, deploying and testing libraries, clients and/or servers. One aspect involves writing and iterating upon the documents that describe the protocols themselves. There are two aspects to protocol development. I'm also excited about future opportunities to evolve on top of QUIC v1 to help build a better Internet. I'm pleased to help shepherd the documents through this important phase, and grateful for the efforts of everyone involved in getting us there, especially the editors. Earlier this year I was honoured to be asked to help co-chair the Working Group. Speaking personally, I've been involved with QUIC in some shape or form for many years now. We are now telling the entire IETF community that we think we're almost done and that we'd welcome their final review. This is an important milestone for the group. On October 21, 2020, following two rounds of Working Group Last Call, draft 32 of the family of documents that describe QUIC and HTTP/3 were put into IETF Last Call. QUIC and HTTP/3 are open standards that have been under development in the IETF for almost exactly 4 years. This enables web pages to load faster, especially over troublesome networks. HTTP/3 builds on top of QUIC, leveraging the new features to fix performance problems such as Head-of-Line blocking. QUIC is a new Internet transport protocol for secure, reliable and multiplexed communications.