WG Action: Rechartered HTTP (httpbis)

The HTTP (httpbis) WG in the Web and Internet Transport of the IETF has been
rechartered. For additional information, please contact the Area Directors or
the WG Chairs.

HTTP (httpbis)
-----------------------------------------------------------------------
Current status: Active WG

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

Assigned Area Director:
  Mike Bishop <mbishop@evequefou.be>

Web and Internet Transport Directors:
  Gorry Fairhurst <gorry@erg.abdn.ac.uk>
  Mike Bishop <mbishop@evequefou.be>

Mailing list:
  Address: ietf-http-wg@w3.org
  To subscribe: ietf-http-wg-request@w3.org
  Archive: http://lists.w3.org/Archives/Public/ietf-http-wg/

Group page: https://datatracker.ietf.org/group/httpbis/

Charter: https://datatracker.ietf.org/doc/charter-ietf-httpbis/

Hypertext Transfer Protocol (HTTP) is an Internet Standard defined in STD 97
/ RFC 9110, with caching behavior in RFC 9111. HTTP semantics are used in
multiple versions, which are mappings to various transports:

  * HTTP/1.1 (RFC 9112)
  * HTTP/2 (RFC 9113), including HPACK (RFC 7541)
  * HTTP/3 (RFC 9114), including QPACK (RFC 9204)

Together, these make up the core specifications of HTTP.

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).

Beyond specification work, the Working Group is a forum for implementers,
practitioners, and researchers to discuss the protocol, its operation and
evolution, to improve interoperability and ecosystem health.

# Work Mode

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 may also make updates to the core HTTP specifications
and existing extensions to clarify existing functionality or address security
issues. These documents may be published as Informational, Experimental, BCP,
or Standards Track at the discretion of the working group.

New extension points, new functionality outside an existing extension point,
and new HTTP versions are not in scope without a recharter.

Work that may need substantial input from other areas (e.g., Security) or
other standards bodies (W3C, etc.) should be coordinated through the
appropriate bodies (such as the responsible Area Director or a general /
'dispatch' group).

Milestones:

   - Submit RFC6265bis (Cookies)

   - Submit Retrofit Structured Fields

   - Submit The HTTP QUERY Method

   - Submit Client-Cert Header

   - Submit Cache Groups

   - Submit Unprompted Auth

   - Submit Compression Dictionaries

   - Submit Resumable Uploads

   - Submit Secondary Server Certs

Received on Monday, 13 October 2025 21:49:26 UTC