Cover Pages Logo SEARCH
Advanced Search
Site Map
CP RSS Channel
Contact Us
Sponsoring CP
About Our Sponsors

Cover Stories
Articles & Papers
Press Releases

XML Query

XML Applications
General Apps
Government Apps
Academic Apps

Technology and Society
Tech Topics
Related Standards

HTTP Revision (http-bis) Charter Proposal

Revised HyperText Transfer Protocol Revision (http-bis) Charter Proposal

[Contains Additional References about the proposed HTTP Working Group as discussed in connection with the 69th IETF, July 22-27, 2007 (Chicago, IL, USA and Hosted by Motorola; see Proceedings.]

Subject: Revised HyperText Transfer Protocol Revision (http-bis) Charter Proposal
From:      Mark Nottingham <>
Date:      Wed, 25 Jul 2007 23:48:35 -0700
Message-Id: <>
To:        HTTP Working Group <>

HyperText Transfer Protocol Revision (http-bis) Charter

Last Modified: 2007-07-25


Applications Area Director(s):
Chris Newman <>
Lisa Dusseault <>

Applications Area Advisor:

Mailing Lists:
General Discussion:
To Subscribe:
In Subject: subscribe Archive:

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 arisen, impairing interoperability and the ability to easily implement and use HTTP to its full potential.

The working group will refine RFC 2616 to:

  • Incorporate errata and updates
  • Improve editorial quality
  • Clarify conformance requirements
  • Remove known ambiguities where they affect interoperability
  • Clarify methods of extensibility
  • Remove or deprecate those features that are not widely implemented, unduly affect interoperability and are not well-supported
  • Where necessary, add implementation advice
  • Document the security properties of HTTP and its associated mechanisms (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 introduce new features or capabilities to HTTP.

The Working Group's specification deliverables are:

  • A document that is suitable to supersede RFC 2616
  • A document cataloguing the security properties of HTTP

Additionally, the Working Group should review (and may document) test suites for HTTP conformance, as they are made available.

Goals and Milestones:
Sep 2007 - First HTTP Revision Internet Draft
Nov 2007 - First HTTP Security Properties Internet Draft
Dec 2007 - IETF 70 Meeting, Vancouver, BC, Canada
Mar 2008 - IETF 71 Meeting, Philadelphia, PA, USA
Apr 2008 - Request Last Call for HTTP Revision
May 2008 - Request Last Call for HTTP Security Properties
Jul 2008 - IETF 72 Meeting, TBD
Aug 2008 - Submit HTTP Revision to IESG for consideration as
           a Draft Standard
Aug 2008 - Submit HTTP Security Properties to IESG for
           consideration as Informational

Mark Nottingham

This archive was generated by hypermail 2.2.0+W3C-0.50:
Thursday, 26 July 2007 06:49:51 GMT



Additional References

HTTPbis BOF, IETF 69, Chicago with BOF Chairs Mark Nottingham and Alexey Melnikov

Meeting Agenda for HTTPbis BOF, IETF 69

BoF Summary, by Mark Nottingham

Draft Minutes from HTTPBis BOF

HyperText Transfer Protocol Revision (http-bis) Charter [2007-07-25]

RFC2616bis Issues

Mail Archives for ''. Collects issues on RFC 2616, and proposes
resolutions for inclusion in a future RFC2616bis. Refer to this list for ongoing discussion.

Hypertext Transfer Protocol -- HTTP/1.1 (draft-lafon-rfc2616bis-03)
Obsoletes: 2616 (if approved) with/vs 2616:

Problems with HTTP State Management, IETF HTTP WG BoF, Yngve N. Pettersen

HTTP ETag on PUT Issues, Cyrus Daboo

Prepared by Robin Cover for The XML Cover Pages archive.

Globe Image

Document URI:  —  Legal stuff
Robin Cover, Editor: