WG Review: HTTP (httpbis)

The HTTP (httpbis) WG in the Web and Internet Transport of the IETF is
undergoing rechartering. The IESG has not made any determination 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 2025-10-05.

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. However, the
chairs may ask that some discussions be moved off-list to avoid interfering
with specification work.

# 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 Chairs judge that there is consensus to take on the item;
and

* The Area Director is informed of the addition.

The Working Group may make minor revisions to the core HTTP drafts under the
same criteria. Major revisions and new HTTP versions are not in scope without
a recharter.

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

Milestones:

TBD

Received on Thursday, 25 September 2025 16:26:14 UTC