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

Re: WG Review: HyperText Transport Protocol Bis (httpbis)

From: Lisa Dusseault <lisa@osafoundation.org>
Date: Fri, 12 Oct 2007 10:28:31 -0700
Message-Id: <E30AF734-E129-4C6D-8490-ADE3FEE264AF@osafoundation.org>
To: HTTP Working Group <ietf-http-wg@w3.org>

Along with input on the charter, I'd appreciate suggestions,  
nominations and maybe even arm-twisting for finding chairs and editors.

thanks,
Lisa

On Oct 11, 2007, at 10:15 AM, IESG Secretary wrote:

> A new IETF working group has been proposed in the Application Area.
> The IESG has not made any determination as yet.  The following draft
> charter was submitted, and is provided for informational purposes  
> only.
> Please send your comments to the IESG mailing list (iesg@ietf.org) by
> October 17.
>
> +++
>
> HyperText Transport Protocol Bis (httpbis)
> ===========================================
>
> Current Status: Proposed Working Group
>
> Chairs:
> TBD
>
> Application Area Director(s):
> Chris Newman <chris.newman@sun.com>
> Lisa Dusseault <lisa@osafoundation.org>
>
> Mailing list:
> http://lists.w3.org/Archives/Public/ietf-http-wg/
>
> Description:
>
>> 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, ABNF)
>> * Fix editorial problems which have led to misunderstandings of
>> the specification
>> * 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
>> 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
>>
>> Goals and Milestones:
>> Nov 2007 - First HTTP Revision Internet Draft
>> Dec 2007 - IETF 70 Meeting, Vancouver, BC, CA
>> Feb 2008 - First HTTP Security Properties Internet Draft
>> Mar 2008 - IETF 71 Meeting, Philadelphia, PA, USA
>> Jun 2008 - Request Last Call for HTTP Revision
>> Jul 2008 - IETF 72 Meeting, TBD
>> 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
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
Received on Friday, 12 October 2007 17:28:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:22 GMT