IETF Logo Mail Archive

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

Bron Gondwana <brong@fastmailteam.com> Tue, 14 July 2020 01:50 UTC

Return-Path: <brong@fastmailteam.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C95A63A0D6C for <dispatch@ietfa.amsl.com>; Mon, 13 Jul 2020 18:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[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_MSPIKE_H3=-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=fastmailteam.com header.b=4IxWw/Af; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CCZ+sqTF
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbG8YRpwY6xJ for <dispatch@ietfa.amsl.com>; Mon, 13 Jul 2020 18:50:04 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F7743A0976 for <dispatch@ietf.org>; Mon, 13 Jul 2020 18:50:04 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AA7AB5C01ED for <dispatch@ietf.org>; Mon, 13 Jul 2020 21:50:03 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Mon, 13 Jul 2020 21:50:03 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm3; bh=WlUtpdE 0FoP3dHgAbw1fbT/E7RjU8VH8w83ZXmFX45w=; b=4IxWw/AfnbKSY2b+N/mCNW1 kx/RO5wbh6lZZejUF1esyLuHwtGU32CKm390t/59tKxoLxk3B8VpSAlwpC8t9hKt K1KF0cvYlEx5FT6WuD52Ta9ovDCNlkXLUzpklKlH0pIVgptHLuj3BYkUZzu831Uc meZSPGlgLUhfKVo/tLQ0s2jQwAEXKvrxqHlNOqhK6kdp0sZfWuylbAftqgH+hnOR 4WGaP4fJnxaYKY6iMMvDYg4pemt6gh4sFaGqiw9S0VZksLgFVmYdEVvFpxLbvOqt fhSv05893TBkMSUbgeFYXS7vGiLMixmXk+vppm56fyie5ENltPjjnOEkm+k23oQ= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :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=WlUtpd E0FoP3dHgAbw1fbT/E7RjU8VH8w83ZXmFX45w=; b=CCZ+sqTF7baQUXxrkl+2lA xV36IyYIk4UwGPuwys9AJClWep6FJ5JXG5EC32cVTWKQEDpUfI7y1dTGa2XGynos J9rIgpo77lcLgU0L+reUPLvLmsNMDYTLdkr4q9UHGEb65mTJQW5LUlPWxFfYgieS rSWf/eewo0lHV+TZuCIDJnYkNe/7Xl5roQI9KPTyknkL+6/LA4vfUos2uuFMVsMu WxaNoMGGCVRZ+2In8UY9u83omRu9v0CxfdqInZdyX+kHZBPmWkyvjIyldJB7wXqR GHoYlKzm36IaeBnTR+HmOGimOksB2nv9qvBF+KCFJ4U9okZG7wxJBhzym3e9V7Qw ==
X-ME-Sender: <xms:Sw8NX4koTxOT4VzYF18xrxEdmz7DE-4fTuwSt7GFSqiKuVizxNGJrg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrvdelgdegkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepvdduueeihefgvd ehueeujeejuedugfeigfevteefleetfeffgfdtjeejgfeuuddvnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrih hlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:Sw8NX310YcuyDlP_GYU_i_jx9Wu2sDUPja7l_lboaqVOCyRUZahCzg> <xmx:Sw8NX2o_w-dr8x0Wtg87bLAbOGe20a5I5kQULAmi92JTvko7dR4buA> <xmx:Sw8NX0motr8YDnvdP7xzYto2TVgaZiCpTAcwgSjuQm84ARnMTEY1bA> <xmx:Sw8NX53uTGrWqU7XViRwfVKcXNZqBY3CL7Hm6ySul0wWpEiZRfCu-A>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3E467180125; Mon, 13 Jul 2020 21:50:03 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-637-g57f734b-fm-idx2020-20200709.002-g57f734bf
Mime-Version: 1.0
Message-Id: <5e605403-e34c-4078-9bea-a57f35aac674@dogfood.fastmail.com>
In-Reply-To: <111A89F4-CBD6-4C63-A45A-C7458E7413FF@mnot.net>
References: <111A89F4-CBD6-4C63-A45A-C7458E7413FF@mnot.net>
Date: Tue, 14 Jul 2020 11:49:41 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="a88ab5ee848245799bba2e23c24d27e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/HuIK0nVt7EZ2h_ClzpLhqDgFTG4>
Subject: Re: [dispatch] A WG for HTTP API Building Blocks
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jul 2020 01:50:06 -0000

On Tue, Jul 14, 2020, at 11:36, Mark Nottingham wrote:
> 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]

I support this idea.

> 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

Particularly with such a large set of evidence in favour of the need for it!

I do feel that there's some crossover to consider with the WPACK working group's work and non-realtime transfer of data.

Cheers,

Bron.

--
 Bron Gondwana, CEO, Fastmail Pty Ltd
 brong@fastmailteam.com

v2.23.0 | Report a Bug | By Email