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 <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
Chair(s):
[TBD]
Applications Area Director(s):
Chris Newman <Chris.Newman@sun.com>
Lisa Dusseault <lisa@osafoundation.org>
Applications Area Advisor:
[TBD]
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 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 http://www.mnot.net/
This archive was generated by hypermail 2.2.0+W3C-0.50:
Thursday, 26 July 2007 06:49:51 GMT
Source: http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0098.html
Comments:
http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0276.html
http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0111.html
http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0107.html
http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0106.html
http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0105.html
Additional References
HTTPbis BOF, IETF 69, Chicago with BOF Chairs Mark Nottingham and Alexey Melnikov
http://www3.ietf.org/proceedings/07jul/slides/httpbis-2/sld1.htm
Meeting Agenda for HTTPbis BOF, IETF 69
http://www3.ietf.org/proceedings/07jul/agenda/httpbis.txt
BoF Summary, by Mark Nottingham
http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0097.html
Draft Minutes from HTTPBis BOF
http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0137.html
http://www3.ietf.org/proceedings/07jul/minutes/httpbis.txt
HyperText Transfer Protocol Revision (http-bis) Charter [2007-07-25]
http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0098.html
RFC2616bis Issues
http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/issues/
Mail Archives for 'ietf-http-wg@w3.org'. Collects issues on RFC 2616,
and proposes
resolutions for inclusion in a future RFC2616bis. Refer to this list for ongoing discussion.
http://lists.w3.org/Archives/Public/ietf-http-wg/
Hypertext Transfer Protocol -- HTTP/1.1 (draft-lafon-rfc2616bis-03)
Obsoletes: 2616 (if approved)
http://ietfreport.isoc.org/idref/draft-lafon-rfc2616bis/ with/vs 2616:
http://www.ietf.org/rfc/rfc2616.txt
Problems with HTTP State Management, IETF HTTP WG BoF, Yngve N. Pettersen
http://www3.ietf.org/proceedings/07jul/slides/httpbis-1.pdf
HTTP ETag on PUT Issues, Cyrus Daboo
http://www3.ietf.org/proceedings/07jul/slides/httpbis-0.pdf
Prepared by Robin Cover for The XML Cover Pages archive.