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

Rob Sayre <sayrer@gmail.com> Thu, 30 July 2020 03:18 UTC

Return-Path: <sayrer@gmail.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 7940E3A0C32 for <dispatch@ietfa.amsl.com>; Wed, 29 Jul 2020 20:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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=gmail.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 bbCbvrhsfJXa for <dispatch@ietfa.amsl.com>; Wed, 29 Jul 2020 20:18:44 -0700 (PDT)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 9D9D83A0C2D for <dispatch@ietf.org>; Wed, 29 Jul 2020 20:18:44 -0700 (PDT)
Received: by mail-il1-x133.google.com with SMTP id l17so11084792ilq.13 for <dispatch@ietf.org>; Wed, 29 Jul 2020 20:18:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GKHt+Ewi7sSTf68Jt3M7jGKISTRIJnb1dtiR32NO8pA=; b=YVB0pG7uViAQd51lI5ILbjFlBmuVZd7REzKqOl3Rm6lMFWxGGTh2cmENozfpAp2RGB 0fMv9iMjeQ2EwjTEZT1tQz9iE8fYhqI7KNYSEGWSvVnEIdwzFXTTaiSZYZbN+kOPi3Tn rZRtvqVzkYYwHoNebNBZnqVkBUoPwoTMN+JWYMFqwXG5h2HGInP/cvcBGHsJhH415HUp 26liwNO9mBCWNEEtv1YHvYoXDrFLuxtNUoBC/m5w4hYh/r0l+VRKam3quYsgKGKdZtkT u6TOPVRIgP6EgHVWk2OVmUpQdz3mrBq+DEXHM5Kq5iAkpsmWb9s1p12snbB55viQ5txB gS6w==
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=GKHt+Ewi7sSTf68Jt3M7jGKISTRIJnb1dtiR32NO8pA=; b=UBVy2Oo/s084JG/e7RWEoM+6w4tjRnZBzOHcBMnJ1O3f4mjqjeYFuEkIUgUVhTHxZm MbO5dOmy2Z2uaeonZzJETG73eRMVuKKmZK0+d9SjSbCsJme1tX5rS1Tj1A0LRqDW8x5L js6Jaltb2NQJVQW4b/36PvXwYtppaXrXfNESFJQU+WATLslhPsZ/1rCn/jQWh0iqXRA/ 0N9kKcOkCQwAPmW2MOztr01my3h+znuPnKgN823At/woJF1BgyOr9RNImdhDhXxQ0i/j fyFEA1pe99HE2p5xtRd3xPu1dYZ5krX8XYE/VKf7vzveBzi025bAvIDVLYKnSoBeBtYQ p2og==
X-Gm-Message-State: AOAM532UrnzTZ04qNzfGQe/VIaZWTTkHROYjx8+zEHgGbJIF4CzwT+7r Hd7izU/sEAkIfnf7NXpK3MABYoCAjxxAILK+GsDpRbxQAGQVZw==
X-Google-Smtp-Source: ABdhPJyxTftTO/pZnen57MtIPuP8uQRBmLk9fL8nIENmirl3uawLWyz8x07AGQMQ47OkFRCh13DubTP/EgTVcJW/Sks=
X-Received: by 2002:a92:858d:: with SMTP id f135mr21379276ilh.257.1596079123805; Wed, 29 Jul 2020 20:18:43 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6SzbYQzn9HLUe4Lq23N9BGXF35NvmHZxYNV485r4D04g-w@mail.gmail.com> <DM6PR00MB08455FC9C8F45CED0A416611F0700@DM6PR00MB0845.namprd00.prod.outlook.com>
In-Reply-To: <DM6PR00MB08455FC9C8F45CED0A416611F0700@DM6PR00MB0845.namprd00.prod.outlook.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Wed, 29 Jul 2020 20:18:31 -0700
Message-ID: <CAChr6Syx0i012db+hPyp+7aJu-Tb2p5TojEJAq6oa+992AH_=w@mail.gmail.com>
To: Darrel Miller <Darrel.Miller=40microsoft.com@dmarc.ietf.org>
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000353a0a05aba0213f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/4R5Cl8RKP2T3qH60dZqxSVZb2Ts>
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 03:18:47 -0000

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