2.1.4 Hypertext Transfer Protocol Bis (httpbis)

NOTE: This charter is a snapshot of the 75th IETF Meeting in Stockholm, Sweden. It may now be out-of-date.

Last Modified: 2008-08-21


Mark Nottingham <mnot@pobox.com>

Applications Area Director(s):

Lisa Dusseault <lisa.dusseault@gmail.com>
Alexey Melnikov <alexey.melnikov@isode.com>

Applications Area Advisor:

Lisa Dusseault <lisa.dusseault@gmail.com>

Mailing Lists:

General Discussion: ietf-http-wg@w3.org
To Subscribe: http://lists.w3.org/Archives/Public/ietf-http-wg/

Description of Working Group:

HTTP is one of the most successful and widely-used protocols on the
Internet today. However, its specification has several editorial
issues. Additionally, after years of implementation and extension,
several ambiguities have become evident, impairing interoperability
and the ability to easily implement and use HTTP.

The working group will refine RFC2616 to:
* Incorporate errata and updates (e.g., references, IANA registries,
* Fix editorial problems which have led to misunderstandings of the
* Clarify conformance requirements
* Remove known ambiguities where they affect interoperability
* Clarify existing methods of extensibility
* Remove or deprecate those features that are not widely implemented
and also unduly affect interoperability
* Where necessary, add implementation advice
* Document the security properties of HTTP and its associated
echanisms (e.g., Basic and Digest authentication, cookies, TLS) for
common applications

In doing so, it should consider:
* Implementer experience
* Demonstrated use of HTTP
* Impact on existing implementations and deployments

The Working Group must not introduce a new version of HTTP and should
not add new functionality to HTTP. The WG is not tasked with producing
new methods, headers, or extension mechanisms, but may introduce new
protocol elements if necessary as part of revising existing
functionality which has proven to be problematic

The Working Group's specification deliverables are:
* A document that is suitable to supersede RFC 2616
* A document cataloguing the security properties of HTTP

Goals and Milestones:

Done  First HTTP Revision Internet Draft
Feb 2008  First HTTP Security Properties Internet Draft
Jun 2008  Request Last Call for HTTP Revision
Jul 2008  Request Last Call for HTTP Security Properties
Oct 2008  Submit HTTP Revision to IESG for consideration as a Draft Standard
Oct 2008  Submit HTTP Security Properties to IESG for consideration as Informational


  • draft-ietf-httpbis-p1-messaging-07.txt
  • draft-ietf-httpbis-p2-semantics-07.txt
  • draft-ietf-httpbis-p3-payload-07.txt
  • draft-ietf-httpbis-p4-conditional-07.txt
  • draft-ietf-httpbis-p5-range-07.txt
  • draft-ietf-httpbis-p6-cache-07.txt
  • draft-ietf-httpbis-p7-auth-07.txt
  • draft-ietf-httpbis-method-registrations-02.txt

    No Request For Comments

    Meeting Minutes


    HTTPbis draft -07 change overview
    HTTP and RFC2231