Version 80 (modified by julian.reschke@…, 10 years ago) (diff)

add diff links


This is the wiki home of the IETF HTTPbis Working Group. We're chartered to:

  • Revise and clarify RFC2616 -- the HTTP 1.1 specification -- to improve interoperability and security, and
  • Develop the next version of HTTP -- HTTP/2.0.

  1. HTTP/1.1 Deliverables
  2. HTTP/2.0 Deliverables
  3. Issue Handling
  4. Participate
  5. People

HTTP/1.1 Deliverables

The HTTP/1.1 specification has been split up into several drafts for readability and modularity; see the Drafts directory for a current snapshot of all HTTP-related drafts.

Additionally, we're publishing:

WGLC indicates a document in Working Group Last Call. p3 was folded into p2.

Past work includes:

Related material includes:

New issues on them can be raised by sending e-mail to the list (see below). It helps to call attention to them in the Subject line (e.g., "NEW ISSUE: ..."). Currently, the group doesn't officially work on new HTTP features, as that's outside the scope of our charter. However, they are often discussed informally on our list, because there are a large number of interested HTTP implementers, and because we may take on new work with a recharter in the future. We track these as PotentialWork.

HTTP/2.0 Deliverables

We're also chartered to work on a replacement for how HTTP is expressed "on the wire." This effort is known as "HTTP/2.0", although it is not a ground-up rewrite of the protocol.

The basis of the work is SPDY. However, we will be collecting issues against this document, as well as confirming consensus over individual portions.

Related material includes:

See the Git repository's README for details of how to provide input to HTTP/2.0.

Issue Handling

For all deliverables, we have two basic types of issues; "design" and "editorial".

Design issues need to be discussed by the Working Group to reach consensus. This generally happens on the mailing list when the issue is raised, but the editors sometimes incorporate a proposed resolution to a design issue in a draft, so that the WG can see it in-situ. Such tickets aren't fully closed until the group confirms the proposal after it is published.

Editorial issues can be resolved by the editors without consultation with the group, although sometimes an editor will poll the group for advice.


As with all IETF Working Groups, almost all discussion and decisions are made on our mailing list. Joining this list is "joining" the Working Group, and is the best way to participate.

We meet at least twice a year at IETF meetings; see also materials from past meetings.

During our official meetings, we use an XMPP (Jabber) channel at xmpp:// (archives) provided by the IETF.

ALL contributors and participants in the Working Group (i.e., on the mailing list and in physical meetings) MUST read and understand the NOTE WELL statement.


Many people have contributed to HTTP's development over the years, and likewise there are many people participating in HTTPbis. The people holding official positions in this effort are: