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

mca <mca@amundsen.com> Thu, 30 July 2020 13:23 UTC

Return-Path: <mca@amundsen.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 3EAED3A1129 for <dispatch@ietfa.amsl.com>; Thu, 30 Jul 2020 06:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=amundsen-com.20150623.gappssmtp.com
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 HEUoWveFXN8j for <dispatch@ietfa.amsl.com>; Thu, 30 Jul 2020 06:23:18 -0700 (PDT)
Received: from mail-oo1-xc2b.google.com (mail-oo1-xc2b.google.com [IPv6:2607:f8b0:4864:20::c2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD8F53A1127 for <dispatch@ietf.org>; Thu, 30 Jul 2020 06:23:18 -0700 (PDT)
Received: by mail-oo1-xc2b.google.com with SMTP id k4so824476ooa.9 for <dispatch@ietf.org>; Thu, 30 Jul 2020 06:23:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amundsen-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IOmbL3z23evx/VpOPZz698yIrxRTqN3lCJ8akP6Zgro=; b=hKDGssXp6akowAjcN4Q+1TJ70JBXtNsvSs9ABF6oDeXA2d1Xk1jf/cVTl0rY5UR3YD oBH3kgd2SFawCCzvOFxv9+LZkE/XIfScjk9uHGJtornhdjHjG71fVaXJURDjtT36bZoC S9kaztGfSbNBcE5pqmfkOrPSy/oeU54MUiMCTR2+BxWt5rKBjKQ+6ADthigzfzdc21Pu DG6HzmyMNNGLLypJ/tgpec7s/aHdgz+MfH46mpxW/wqfBrtC6ZkqHjhiT9go2TAP73KB kPxqUVr1f8nwZzAdA7TUyKRRPm7GSb1BjA7oXnyHBHXVRYa0j1pfloOrhQUXjij57Xer RcXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IOmbL3z23evx/VpOPZz698yIrxRTqN3lCJ8akP6Zgro=; b=LOwn6ruko/XUraC214l5zM3HiEmROMCUrvWCvKlUtuETtKa/yiEouYTHVxt+smQTer rhZlYNbtuGEz1jgPvM0eWXXoM1klw2R+jvsmR+5wZwsD6PWPPhHan/AYcaq+TJFKjj6j nZVepnCJxvrin3EbUEc0EjiJ0FoLeSZq8ksxRo1WH5HZNE1/FHCJfXZpS0hW4DOEhj5n YhHJ5okZ1ebM8tTt/Wq9GW5lTzhX4zZN0CeADes18TBaU7t+UyecYVqntuvcKVSgjXKb kW4clk3FVVIaSxu/qqPH+NhYe3JGVwZQfShFgrG5SJbCycZnnzwH7I9nTJwBiiVv3Sk3 YAhg==
X-Gm-Message-State: AOAM531G/ikUQRS+b9QxzwUP8IFfbtIj3ixssXVaNqgl1fpisHVSjN9K 0z5/9FMkwSK8DrL6M8Lmg6NgRoIJdgfRBmH5UMw46Q==
X-Google-Smtp-Source: ABdhPJzimFzxpZ/dboxjnnw+Uzcw/DINxOZpyqXCRQdqVPGW+tdLSkoSKrEOWRArsST/PMk37eL10SYbMp6nVV2L608=
X-Received: by 2002:a4a:7241:: with SMTP id r1mr2403319ooe.48.1596115397484; Thu, 30 Jul 2020 06:23:17 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6SzbYQzn9HLUe4Lq23N9BGXF35NvmHZxYNV485r4D04g-w@mail.gmail.com> <DM6PR00MB08455FC9C8F45CED0A416611F0700@DM6PR00MB0845.namprd00.prod.outlook.com> <CAChr6Syx0i012db+hPyp+7aJu-Tb2p5TojEJAq6oa+992AH_=w@mail.gmail.com>
In-Reply-To: <CAChr6Syx0i012db+hPyp+7aJu-Tb2p5TojEJAq6oa+992AH_=w@mail.gmail.com>
From: mca <mca@amundsen.com>
Date: Thu, 30 Jul 2020 09:23:06 -0400
Message-ID: <CAPW_8m4P7GDFX0cHxeuAYfxx3+7-iMt8E75W1s9U5xG9j1hH0Q@mail.gmail.com>
To: Rob Sayre <sayrer@gmail.com>
Cc: Darrel Miller <Darrel.Miller=40microsoft.com@dmarc.ietf.org>, "dispatch@ietf.org" <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000049c2ab05aba893ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/PXgI9jeQnxQvkgJ0pOMDbPJUhik>
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: Thu, 30 Jul 2020 13:23:22 -0000

I was unable to attend so please pardon my digressions and miscues -- feel
free to point me in the right direction.

Per points one and two in the proposed chapter, I think there are a a few
possible sources of content for definitions/specs related to
machine-to-machine APIs.

- Subbu Alamaraju's "RESTful Web Services Cookbook" [1] identifies a
collection of recipes to solve common API problems over HTTP and might be
fertile ground for defining headers, bodies and a handful of common
practices.
- My talk/slides on Hypermedia Patterns [2] has a handful of elements that
could be improved over HTTP w/ some body/header/status work
- I assume there are others, too

As for point three, I'd also like to see the group continue to focus on
best practices and steer clear of attempting to define API sets to solve
particular problems.




[1]
https://books.google.com/books/about/RESTful_Web_Services_Cookbook.html?id=ed5ml0T3zyIC
[2] http://amundsen.com/talks/2017-04-craftconf/index.html

Mike Amundsen

*APIs, Microservices, and Digital Transformation*
7310 Turfway Rd. Suite 550, Florence, KY, 41042


*+1.859.372.6517*
https://zoom.us/j/8593726715
http://linkedin.com/in/mamund
http://g.mamund.com/meetme
http://training.amundsen.com
http://twitter.com/mamund



On Wed, Jul 29, 2020 at 11:19 PM Rob Sayre <sayrer@gmail.com> wrote:

> On Wed, Jul 29, 2020 at 8:06 PM Darrel Miller <Darrel.Miller=
> 40microsoft.com@dmarc.ietf.org> wrote:
>
>>
>> - Long running operations that return a 202 Accepted header and reference
>> a “status monitor” resource. This is a topic that comes up regularly.
>>
>> - Resumable large file uploads is a tricky topic that if I recall was
>> discussed at last years HTTP Workshop.
>>
>
> Thanks for the thoughtful response, most of which can be better answered
> by others.
>
> On these two quoted related topics, I can answer. You just want something
> like this: https://aws.amazon.com/blogs/aws/amazon-s3-multipart-upload/
>
> I think the AWS minimum chunk size is too large, but otherwise this API or
> something like it (there are many clones), would be fine..
>
> thanks,
> Rob
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>