* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Httpbis Status Pages

HTTP (Active WG)
Art Area: Francesca Palombini, Murray Kucherawy | 2007-Oct-23 —  

2021-03-22 charter

HTTP (httpbis)


 Current Status: Active

     Mark Nottingham <mnot@mnot.net>
     Tommy Pauly <tpauly@apple.com>

 Applications and Real-Time Area Directors:
     Murray Kucherawy <superuser@gmail.com>
     Francesca Palombini <francesca.palombini@ericsson.com>

 Applications and Real-Time Area Advisor:
     Francesca Palombini <francesca.palombini@ericsson.com>

 Mailing Lists:
     General Discussion: ietf-http-wg@w3.org
     To Subscribe:       ietf-http-wg-request@w3.org
     Archive:            http://lists.w3.org/Archives/Public/ietf-http-wg/

Description of Working Group:

  This Working Group is charged with maintaining and developing the "core" specifications for HTTP, and generic extensions to it (i.e., those that are not specific to one application).

  Its current work items are:

  # HTTP/1.1 Revision

  After the revision of the core HTTP document set in the RFC723x series, the Working Group published HTTP/2, which defines an alternative mapping of HTTP's semantics to TCP, and introduced new capabilities, like Server Push.

  Additionally, several ambiguities, interoperability issues and errata have been identified since their publication.

  The Working Group will revise the "core" HTTP document set (RFC 7230-RFC 7235) to:

  * Incorporate errata

  * Address ambiguities

  * 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

  In doing so, it should consider:

  * Implementer experience

  * Demonstrated use of HTTP

  * Impact on existing implementations and deployments

  # HTTP and QUIC

  Upon request from the QUIC Working Group, the HTTPBIS Working Group will review the QUIC Working Group's documents regarding the use of HTTP over the transport protocol they define, providing feedback and collaborating where necessary.

  Once the QUIC Working Group publishes the expression of HTTP semantics in QUIC (HTTP/3), the HTTPBIS Working Group will maintain and develop extensions for HTTP/3 as necessary. This includes ancillary specifications (e.g. QPACK).

  # Other HTTP-Related Work

  The Working Group may define extensions and other documents related to HTTP as work items, provided that:

  * They are generic; i.e., not specific to one application using HTTP. Note that Web browsing by definition is a generic use.

  * The Working Group Chairs judge that there is consensus to take on the item and believe that it will not interfere with the work described above, and

  * The Area Director approves the addition and add corresponding milestones.

Goals and Milestones:
  Jun 2020 - Submit the "core" HTTP documents for consideration as Internet Standards
   - Submit RFC6265bis (Cookies)
   - Submit Client Hints
   - Submit Structured Headers
   - Submit Secondary Certificates
   - Submit Building Protocols with HTTP (BCP56bis)
   - Submit HTTP Representation Variants
   - Submit Cache-Status Header
   - Submit Proxy-Status Header
   - Submit Digest Headers

All charter page changes, including changes to draft-list, rfc-list and milestones:

Generated from PyHt script /wg/httpbis/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -