Skip to main content
  • Suggested IETF 123 Sessions for Getting Familiar with New Topics

    These IETF 123 meeting sessions are likely to include discussions and proposals that are accessible to a broad range of Internet technologists whether they are new to the IETF or long-time participants.

    8 Jul 2025
  • Experiences from IGF 2025

    At the Internet Governance Forum 2025 in Norway (23-27 June), the presence of the IETF was well-received as part of the broader effort to strengthen the connection between technical and policy discussions, helping to build trust, increase visibility and highlight the role of the technical community in Internet governance.

    2 Jul 2025
  • Progress on AI Preferences

    In January, the IETF chartered the AI Preferences (AIPREF) Working Group to make it easier to express how AI models should use Internet content. With a compressed timeline for delivery, it’s a good time to update those who haven't been following the work closely.

    29 Jun 2025
  • IETF LLC Board Retreat 2025

    The IETF Administration LLC (IETF LLC) Board met for its annual strategic retreat 6-7 May 2025 in Amsterdam, where it discussed the future strategy of the IETF LLC, as well as high priority operational issues.

    24 Jun 2025
  • Report from the Tools Team Retreat 2025

    The IETF Administration LLC (IETF LLC) development team met along with IETF LLC senior leadership for its annual two-day retreat, and with the IETF Chair able to join remotely for key sessions. This post reviews the key inputs and outputs of that retreat, and how they affect the IETF.

    16 Jun 2025

Filter by topic and date

Filter by topic and date

HTTP/2 Approved

18 Feb 2015

After more than two years of discussion, over 200 design issues, 17 drafts, and 30 implementations, the HTTP/2 and HPACK specifications have now been approved by the IETF’s steering group for publication as standards-track RFCs.

The result is that HTTP/2 will help provide faster user experience for browsing, reduce the amount of bandwidth required, and make the use of secure connections easier.

The HTTP Working Group began work on HTTP/2 in 2012 by selecting Google’s SPDY protocol as the starting point, holding a series of six interim meetings to incorporate community feedback. This resulted in substantial changes to the format of the protocol, its compression scheme, and its mapping to the semantics of HTTP.

The resulting protocol is designed to allow a seamless switch between HTTP/1 and HTTP/2, with minimal changes to applications and APIs, while at the same time offering improved performance and better use of network resources. Web users largely will be able to benefit from the improvements offered by HTTP/2 without having to do anything different.

A key point in the protocol development process was the iteration the working group did between protocol updates, and implementations and testing. Certain draft protocol versions were labelled by the working group as “implementation drafts”, and the participants — many web browser and web server providers — updated their implementations and tested out the protocol changes. Most of the interim meetings included part of a day spent on hands-on interoperability testing and discussion. The result is a thoroughly validated protocol that has been shown to interoperate and that meets the needs of many major stakeholders.

The HTTP/2 work specifically embodies the key IETF tenet about the value of “rough consensus and running code.”

See the HTTP/2 home page, Frequently Asked Questions list (FAQ), and the chair’s blog article for more information. The specifications themselves are available here for HTTP/2 and HPACK.


Share this page