Hypertext Transfer Protocol
charter-ietf-httpbis-09
Document | Charter | HTTP WG (httpbis) | |
---|---|---|---|
Title | Hypertext Transfer Protocol | ||
Last updated | 2025-10-13 | ||
State | Approved | ||
WG | State | Active | |
IESG | Responsible AD | Mike Bishop | |
Charter edit AD | Mike Bishop | ||
Send notices to | (None) |
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).