W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2007

Revised charter proposal

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 25 Jul 2007 23:48:35 -0700
Message-Id: <92689CB1-EADB-496F-A783-BCDA33C76FF7@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>

HyperText Transfer Protocol Revision (http-bis) Charter

Last Modified: 2007-07-25


Applications Area Director(s):
Chris Newman <Chris.Newman@sun.com>
Lisa Dusseault <lisa@osafoundation.org>

Applications Area Advisor:

Mailing Lists:
General Discussion: ietf-http-wg@w3.org
To Subscribe: ietf-http-wg-request@w3.org
In Subject: subscribe
Archive: 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 arisen, impairing interoperability and the  
ability to easily implement and use HTTP to its full potential.

The working group will refine RFC2616 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  
Aug 2008 - Submit HTTP Security Properties to IESG for consideration  
as Informational

Mark Nottingham     http://www.mnot.net/
Received on Thursday, 26 July 2007 06:49:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:31 UTC