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

Httpapi Status Pages

Building Blocks for HTTP APIs (Active WG)
Art Area: Francesca Palombini, Murray Kucherawy | 2020-Oct-23 —  
Chairs
 
 


2021-03-22 charter

Building Blocks for HTTP APIs (httpapi)
---------------------------------------

 Charter

 Current Status: Active

 Chairs:
     Darrel Miller <darrel.miller@microsoft.com>
     Rich Salz <rsalz@akamai.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>

 Secretary:
     Mark Nottingham <mnot@mnot.net>

 Mailing Lists:
     General Discussion: httpapi@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/httpapi
     Archive:            https://mailarchive.ietf.org/arch/browse/httpapi/

Description of Working Group:

  In addition to its use for web browsing, HTTP is often used for machine-to-machine communication, facilitated by HTTP APIs. This Working Group will standardise HTTP protocol extensions for use in such cases, with a focus on building blocks for separate or combined use.

  Its output can include the following:

  • Specifications for HTTP extensions that relate to HTTP APIs (typically, new HTTP header and/or trailer fields)

  • Specifications for new message body formats, or conventions for their use in HTTP APIs (e.g., patterns of JSON objects)

  • Best practices and other documentation for HTTP API designers, consumers, implementers, operators, etc.

  Other items are out of scope. In particular, this WG will not take on work items for HTTP APIs for specific applications or services, and it will not define new HTTP extension points. APIs for HTTP itself (e.g., in clients and servers) are also out of scope.

  To be successful, this Working Group will need to have active and broad representation from across the industry -- e.g., API gateway vendors (and other intermediaries), API consultants, API tool vendors, in-house API teams. Therefore, adopted proposals should have public support from multiple implementers and/or deployments before being sent to the IESG.

  To assess whether the group is functioning well, this charter will be reviewed by the IESG nine months after chartering.

  This Working Group will also need to coordinate closely with the HTTP Working Group, in particular when new methods and status codes are proposed. Work items that are more broadly applicable (e.g., for implementation in Web browsers) are likely to be more appropriate in the HTTP Working Group, but it is expected that coordination and discussion between the groups' Chairs and Area Director(s) will guide work items to the appropriate venue.

Goals and Milestones:


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



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