Skip to main content
  • IETF 126 Highlights

    The IETF 126 meeting was held 18–24 July 2026 at the Hilton Vienna Park in Vienna, Austria, and online, hosted by Cisco. The week included the IETF Hackathon and Code Sprint, the New Participants' Program, five Birds-of-a-Feather (BoF) sessions, and more than 100 working group and research group sessions. The Applied Network Research Workshop also took place during the IETF 126 meeting week.

    1 Sep 2026
  • IETF email infrastructure transition planned for 11 September

    A transition to a new modern, modular, and containerized infrastructure for email services provided for ietf.org, iab.org, irtf.org, rfc-editor.org (including email lists) is scheduled for 11 September 2026 starting at 2200UTC, with message delivery delayed up to 60 minutes. Further updates will be provided closer to the transition.

    28 Aug 2026
  • Post-Quantum Authentication: Up Next

    Post-quantum key establishment has moved from standards into deployment. Post-quantum authentication has not moved nearly as far, and specification work is no longer the only constraint. The IAB is holding a workshop in Prague on 11 and 12 October 2026 to bring deployment experience together with the people working on the relevant protocols and standards.

    27 Aug 2026
  • IETF 126 post-meeting survey: what we heard

    The IETF 126 Vienna meeting was held 18-24 July 2026 and the results of the post-meeting survey are now available.

    27 Aug 2026
  • Meet our new IETF NOC Lead

    Joe Clarke has been appointed as the new IETF NOC Lead and in this post Joe introduces himself and sets out his priorities for the IETF Network.

    10 Aug 2026

Filter by topic and date

Filter by topic and date

HTTP 2.0

9 Jan 2014

I wanted to draw attention to Mark Nottingham’s excellent blog article about strengthening HTTP.

The article is available from this link. Like his previous posts on the topic, he raises important issues about the design of HTTP 2.0 and how to ensure that we can provide as good security protection as possible for Internet users employing HTTP 2.0.

This is obviously extremely important for the Internet and its evolution. Such a large part of our Internet use happens on the web that its key building blocks matter. And the web protocol stack is not just used by us humans and our browsers; it is also used by countless applications. As an example, the world of intelligent objects around us is to a large extent being constructed on top of the web protocol stack. HTTP 2.0 is likely to see very widespread use as the standard becomes available later this spring.

And improving the security is not easy, as Mark points out. But it is important. Can we do more? How can the current thinking be improved? Please join the discussion at the HTTPBIS working group.


Share this page