Search This Blog

Sunday, October 14, 2007

Proposed Working Group: HyperText Transport Protocol Bis (httpbis)

The Internet Engineering Steering Group has announced the proposal for
a new "HTTP bis" IETF working group in the Application Area, to be
managed by Application Area Director Chris Newman (Sun Microsystems)
and Lisa Dusseault (Open Source Applications Foundation). A draft
Working Group Charter has been submitted for informational purposes.
The IESG has not yet made a determination about formation of the WG,
but solicits public comment through October 17, 2007. Hypertext Transfer
Protocol (HTTP/1.1) was published as IETF Standards Track Request for
Comments (RFC) #2616 in June 1999. Its editors include Roy T. Fielding,
James Gettys, Jeffrey C. Mogul, Henrik Frystyk Nielsen, Larry Masinter,
Paul J. Leach, and Tim Berners-Lee. According to the proposed WG Charter,
"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
RFC 2616 to: (1) Incorporate errata and updates -- e.g., references,
IANA registries, ABNF; (2) Fix editorial problems which have led to
misunderstandings of the specification; (3) Clarify conformance
requirements; (4) Remove known ambiguities where they affect
interoperability; (5) Clarify existing methods of extensibility; (6)
Remove or deprecate those features that are not widely implemented
and also unduly affect interoperability; (7) Where necessary, add
implementation advice; (8) Document the security properties of HTTP
and its associated mechanisms (e.g., Basic and Digest authentication,
cookies, TLS) for common applications). In making these refinements,
the WG should consider implementer experience, demonstrated use of HTTP,
and the 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: [i] a document that is suitable to
supersede RFC 2616, and [ii] a document cataloguing the security
properties of HTTP. More Information See also the RFC2616bis Issues list: Click Here

No comments: