Skip to main content
  • IETF Administration LLC 2026 Budget

    A draft budget was shared previously for community consultation and the IETF Administration LLC now has finalised its budget for 2026.

    28 Jan 2026
  • Agentic AI communications: Identifying the standards we need

    When it comes to standards work around agentic AI, we’re at an exciting threshold. As more tools emerge, we’re seeing the amazing things it can accomplish. Now, we’re trying to figure out what parts of it need to be standardized.

    22 Jan 2026
  • IETF@40

    Forty years ago today, 21 people gathered in San Diego, California for the first meeting of what became the Internet Engineering Task Force.

    16 Jan 2026
  • Launch of the IETF Community Survey 2025

    The IETF Community survey is our major annual survey of the whole of the IETF community and is used to inform the actions of IETF leadership throughout the year. The 2025 IETF Community Survey is live and we want to hear from you!

    23 Dec 2025
  • IETF Administration LLC 2026 Draft Budget

    The IETF Administration LLC has prepared its draft budget for 2026 and now seeks community feedback.

    19 Dec 2025

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