Fwd: [dispatch] A WG for HTTP API Building Blocks

Mark Nottingham <mnot@mnot.net> Wed, 15 July 2020 06:58 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5D7F13A0433 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Jul 2020 23:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.018
X-Spam-Status: No, score=-3.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=hRKngs+L; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=G1dowcac
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id efJLUrKPPb6H for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Jul 2020 23:58:43 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3DF33A043D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 14 Jul 2020 23:58:42 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jvbKM-0008Eh-FV for ietf-http-wg-dist@listhub.w3.org; Wed, 15 Jul 2020 06:55:38 +0000
Resent-Date: Wed, 15 Jul 2020 06:55:38 +0000
Resent-Message-Id: <E1jvbKM-0008Eh-FV@lyra.w3.org>
Received: from titan.w3.org ([]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <mnot@mnot.net>) id 1jvbKL-0008Du-7d for ietf-http-wg@listhub.w3.org; Wed, 15 Jul 2020 06:55:37 +0000
Received: from wout2-smtp.messagingengine.com ([]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <mnot@mnot.net>) id 1jvbKI-0004qo-Eu for ietf-http-wg@w3.org; Wed, 15 Jul 2020 06:55:37 +0000
Received: from compute4.internal (compute4.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id E14F3B08 for <ietf-http-wg@w3.org>; Wed, 15 Jul 2020 02:55:20 -0400 (EDT)
Received: from mailfrontend2 ([]) by compute4.internal (MEProxy); Wed, 15 Jul 2020 02:55:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:mime-version:subject:message-id:references:to :date; s=fm3; bh=YZcgXJqwlieiaXQ7hkrVgB/amaYvIKXquB2K9Y8WA5Y=; b= hRKngs+LfyhjPLXgo9hX3ri55QFt0/Aj7RZDcUw/z9wsIQkC5jFO17PgDW+Yc9c2 +8K49ObYYUaTOVpBpHL9besd9229ox/jqqlk89Tx+68DQ+MUIy9afU3Ss2JD3lqt X5BrFVkMqeSCqxhLsPVCBLnATAM1A6hJ2ukcs3xC5k6pW3NQNFvz1TZzVuh5O9Ly 6NeSYJqz4WWpGAlBibC9x9L+lT6YjdfiO95ZrigyDg7mnlX4mZ3ayKz8IT4MRuFK z+tXA6cYWmGbV1weAGJP+KAl3CnTPcoe+DMpj8sV9UCLm4qcHe9yfKf1D1hXBiHP tYClWdLzDulGh2Kog6PHwA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=YZcgXJqwlieiaXQ7h krVgB/amaYvIKXquB2K9Y8WA5Y=; b=G1dowcac+rgevu3BKUoOkl1cnRF5KHK9b rUKqXHK7RTARHrPM+pcyGGO2sZidQiuqJ+KxmGF6UTBTyNSBJrBrR+4xIXle0qTa yLj/B3LqHsUNfszE/W2O0AbxYb756I6zBWzgZfkBa4KOQlgWZs3iYi5uya9heSee 0nrHK2FDUiI3z1HQ2Ep2VOpDZV3kEsJosf5hMQO2vLIq+LDZCT4m7NMwXAUwvTeQ aQJaGXnQbtTPeQvM0RYDG7tWD3zqSgmwK50nnkrs+A544taS6V0SyVdWSSeHuk2T Ib8LTtCtd1UPRi9Z0d2u7peS1HIPhAmz8udkEXHQXZmLVwRK1IFEg==
X-ME-Sender: <xms:WKgOX5XuzlR3R9aPs8EQ2fWRvcBzgLQzhEwhNsp3-HIFRHQybUkPYA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrfedugdduudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhtggguffkfhfvfffosegrtdhmre hhtdejnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhho thdrnhgvtheqnecuggftrfgrthhtvghrnhepgeeihfduueegffeikeeiheeuudeuhffgff duudffieefheduteffudevhfeihffgnecuffhomhgrihhnpehivghtfhdrohhrghdpmhhn ohhtrdhnvghtnecukfhppeduudelrddujedrudehkedrvdehudenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:WKgOX5mPx3UO7P0fyf5bCrrO2HL-8vFrEBnrbQ4ciecHboypxC7HFQ> <xmx:WKgOX1byZ3cz919UIygPu2AVX5nHHBq-zK_0CVv73oyjouppgPIKRw> <xmx:WKgOX8XeJnuhDfV-hBmTTKRsLSBhan9R73FvoJO-_eOmySBu9pVdfA> <xmx:WKgOXyvEpIym6DqtYZX-huYc6oMfmKqnU78sJLf2MAT8wduPxTOJsA>
Received: from marks-air.mnot.net (119-17-158-251.77119e.mel.static.aussiebb.net []) by mail.messagingengine.com (Postfix) with ESMTPA id 54CD0306005F for <ietf-http-wg@w3.org>; Wed, 15 Jul 2020 02:55:19 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_422AF5E8-569A-459C-87BB-3F62EA562E12"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Message-Id: <539746A9-6BA7-41B6-8E9C-8C8E403B2E27@mnot.net>
References: <111A89F4-CBD6-4C63-A45A-C7458E7413FF@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>
Date: Wed, 15 Jul 2020 16:55:16 +1000
X-Mailer: Apple Mail (2.3608.
Received-SPF: pass client-ip=; envelope-from=mnot@mnot.net; helo=wout2-smtp.messagingengine.com
X-W3C-Hub-Spam-Status: No, score=-9.8
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1jvbKI-0004qo-Eu bb15b8fb4dd34ce5a5a9fed5d3433dc8
X-Original-To: ietf-http-wg@w3.org
Subject: Fwd: [dispatch] A WG for HTTP API Building Blocks
Archived-At: <https://www.w3.org/mid/539746A9-6BA7-41B6-8E9C-8C8E403B2E27@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37880
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

FYI - I've started a discussion in DISPATCH about a proposal for a new HTTP-related WG. See discussion there:


> Begin forwarded message:
> From: Mark Nottingham <mnot@mnot.net>
> Subject: [dispatch] A WG for HTTP API Building Blocks
> Date: 14 July 2020 at 11:36:25 am AEST
> To: DISPATCH WG <dispatch@ietf.org>
> Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/pWx1SgjZS4R3nzXEK-jE6xqOqUc>
> I've been chatting with folks in the background for a while about starting a WG to take on specs to help folks building HTTP APIs.[1]
> HTTP has been used for machine-to-machine communication for most of its lifetime, there are a number of functions that are designed and implemented in an ad hoc fashion, or with several competing approaches. Establishing a WG to standardise some common functions might help, both by documenting some common building blocks, and serving as a locus for a new community -- one that's related to but distinct from the HTTP WG.
> For example, these specifications were either AD-sponsored or on the Independent stream, but could have been in-scope for such a WG:
> - rfc6570 URI Template
> - rfc6892 The 'describes' Link Relation Type
> - rfc6901 JSON Pointer
> - rfc6902 JSON Patch
> - rfc7807 Problem Details for HTTP APIs
> - rfc8288 Web Linking
> - rfc8594 The Sunset HTTP Header Field
> - rfc8631 Link Relation Types for Web Services
> ... and there are also a number of current drafts that such a WG might consider, e.g.:
> - draft-wilde-linkset
> - draft-nottingham-link-hint
> - draft-dalal-deprecation-header
> - draft-polli-ratelimit-headers
> This is the proposed charter:
> ~~~
> HTTP APIs Working Group (HTTPAPI)
> HTTP is often for not only Web browsing, but also machine-to-machine communication, often called '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:
> 	• Specifications for new HTTP header and/or trailer fields
> 	• Specifications for new message body formats, or conventions for use in them (e.g., patterns of JSON objects)
> 	• Proposals for new HTTP status codes, methods, or other generic extensions, to be considered by the HTTP Working Group
> 	• 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 APIs for specific use cases, and it will not define new HTTP extension points, or new extensions that are likely to be used by Web browsers.
> New work items can be added after a Call for Adoption on the working group mailing list and consultation with the Area Director.
> 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.
> This Working Group will need to coordinate closely with the HTTP Working Group.
> ~~~
> Because a large part of the task here is building a representative community, I think this group should be chartered without specific documents; it can deliberate on what's appropriate to start with once constituted. It should also be periodically evaluated to make sure that it's functioning well and representative of the greater community, with the assumption that if it isn't, it would be closed (I'd hope that ADs do that for every WG anyway, but since this is trying to establish a new venue, it should be considered on probation).
> The ADs have responded positively, and asked me to bring this to DISPATCH for wider review. I'm happy to talk about it in the meeting if there's time.
> Cheers,
> 1. a.k.a. "RESTful APIs", although that's a misunderstanding of what REST is.
> --
> Mark Nottingham   https://www.mnot.net/
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

Mark Nottingham   https://www.mnot.net/