Skip to main content
  • New RFC Editor website is live

    Today we are launching the new rfc-editor.org website, the most visible part of a comprehensive overhaul of the tools that support editing and publishing RFCs.

    20 May 2026
  • IETF 125 Highlights

    More than 1500 participants gathered in Shenzhen and online for the IETF 125 meeting 14-20 March 2026 for more than 100 working sessions, an IETF Hackathon, and more.

    19 May 2026
  • Report from the 2026 RPC Retreat

    The RFC Production Center (RPC) retreat was a two-day strategic planning session taking place the week of April 20 that gathered the entire RPC team and IETF Administration senior staff.

    18 May 2026
  • A new suite of modern tools coming for editing and publishing RFCs

    After a number of years of work, the initial rollout of a modern suite of tools for editing and publishing RFCs, including an entirely new rfc-editor.org website, will take place in May 2026.

    12 May 2026
  • IETF Snapshot 2025

    Want to catch up on IETF activity in 2025? How many RFCs were published? How many Internet-Drafts were submitted? How many Working Groups were chartered or concluded? The latest edition of the IETF Snapshot provides a recap of IETF activity for the previous year.

    12 May 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