HTTPBIS WG Wiki

This is the wiki of the IETF HTTPBIS Working Group. We're ​chartered to revise and clarify RFC2616 -- the HTTP 1.1 specification -- to improve interoperability and security.

Deliverables

The HTTP 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.

• ​p1: Messaging - low-level message parsing and connection management
• ​p2: Semantics - methods, status codes and headers
• ​http://tools.ietf.org/wg/httpbis/draft-ietf-httpbis-p3-payload/ p3: Payload] - dealing with content, message-specific headers
• ​http://tools.ietf.org/wg/httpbis/draft-ietf-httpbis-p4-conditional/ p4: Conditional Requests] - e.g., If-Modified-Since
• ​p5: Range Requests - getting partial content
• ​p6: Caching - browser and intermediary caches
• ​http://tools.ietf.org/wg/httpbis/draft-ietf-httpbis-p7-auth/ p7: Authentication] - HTTP authentication framework

Additionally, we're publishing:

• ​Security Properties - an explanation of the security properties of HTTP
• ​Method Registrations - a document establishing the HTTP method registry's initial contents
• ​Content-Disposition - a specification of how to use the Content-Disposition header in HTTP

Related material includes:

• ​Subversion repository
• ​Document changes, also in ​RSS and on ​Twitter

Currently, the group doesn't officially work on new HTTP features or specifications, as that's outside the scope of ​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.

Issue Handling

Issues with the specifications are kept in our ​ticket tracker.

We have two basic types of issues; Design (​open issues) and Editorial (​open issues).

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; you can see ​a list of such tickets here.

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

New issues 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: ...).

Participate

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.

We use a [xmpp://httpbis@jabber.ietf.org?join XMPP/Jabber channel] (​archives), but usually just during physical meetings.

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.

People

Many people have contributed to HTTP's development over the years, and likewise there are many people participating in HTTPbis. A few people to note in this effort are:

• ​Alexey Melnikov - our Area Director, who oversees the WG for the ​IESG
• ​Mark Nottingham - Working Group Chair, editor for p6 Caching
• [​http://www.julian-reschke.de/ Julian Reschke - Editor, p1-p6, Method Registrations, Content-Disposition
• ​Roy Fielding - Editor, p1-p6
• ​Yves Lafon - Editor, p1-p6
• ​Jeff Hodges - Editor, Security Properties
• ​Barry Lieba - Editor, Security Properties