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

Michael Toomim <toomim@gmail.com> Thu, 16 July 2020 07:56 UTC

Return-Path: <toomim@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 0F9293A105C for <dispatch@ietfa.amsl.com>; Thu, 16 Jul 2020 00:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 CLqexvXA1KCj for <dispatch@ietfa.amsl.com>; Thu, 16 Jul 2020 00:56:11 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 AFFC33A0FA2 for <dispatch@ietf.org>; Thu, 16 Jul 2020 00:56:11 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id x8so3508410plm.10 for <dispatch@ietf.org>; Thu, 16 Jul 2020 00:56:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fHV9Gp8jpZNTq+kBeSKCXi/JA9xHEiOs1hr2K8qYFYs=; b=duMsSA0D/BhXGsHCX4X9sWOCRNhd5A5Mv1j6RjmWqitGqYixBUQcTJ9YMnPnyjrAid hTEWbjhFS4hxkLTVkUfkeG9ZKouHimKdbO4I5k+DYczNrdP27+iEiNKUon+Jsc2EA+o8 xEmvO1ois+SHtpE+FVzdt7lLPf01wQ/WDAf+lYP2HF1268gKw+b2iPAMzsKLbHYrTqCZ rcp6ErCYkCmgJWFqrOMcPET545/sKw4bYA2Vr0zRL7R8wk2DXyFGB88D5cFr53C1x270 SclT6QonaTgLBw2DbZKDCPTNTHAKQkevje6UwhT/31B/KhYl45g+xjUvMHQRcy9LiyBK uvsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fHV9Gp8jpZNTq+kBeSKCXi/JA9xHEiOs1hr2K8qYFYs=; b=PtjYpVa393coxfbtz6qhmQNHwSiv9/chRiFKro6den0Lohq9Ws9bVEnrZg7ulqh6gk dfGo9xIJ6ZrjobtfFSoI6VhkbjE/igR4U9hcGW5KIPO85Xjqf+PV9gqOTxm1X4dw40Fh IwIiUfG2dDg9iJb/zaYJ3zz8zn5E6m5OS6GRuc/N5OyQZUJPkCjFtyK3pdeVHpsPCW1Q Vy2iiIY+fdeoeWhH7zUx/uBxacH6B/YQpcqRmieay1D5CiPaNbPMti4uYQG7bJs4IF6g BlkKUK7UZkxQLOkbwQj2mKlPkh3ESvx3k6t6uS2ZCPOL55vOgIpyVFK5BBasUP0AA088 cZWA==
X-Gm-Message-State: AOAM530dlrUTZj+jJ8h3yEo3YnlDF//AVH2Tmbo77kl1diHeLJsT5vAJ g7AkUNciv5Z/1rISZwCrmYxGK6xu
X-Google-Smtp-Source: ABdhPJzMP/zqJMO1yvcI8NZdjVhxAPaBIsuO07DFvphr/SqML/6U2zH/Z1KrBWzVs3sj8zQko+wO7A==
X-Received: by 2002:a17:90a:eac7:: with SMTP id ev7mr3320232pjb.21.1594886171043; Thu, 16 Jul 2020 00:56:11 -0700 (PDT)
Received: from [192.168.42.5] (135-180-96-53.fiber.dynamic.sonic.net. [135.180.96.53]) by smtp.gmail.com with ESMTPSA id n63sm4167156pfd.209.2020.07.16.00.56.09 (version=TLS1 cipher=ECDHE-ECDSA-AES128-SHA bits=128/128); Thu, 16 Jul 2020 00:56:10 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Michael Toomim <toomim@gmail.com>
In-Reply-To: <B4F7AAFD-BF05-4FF1-A960-827F237C02BB@mnot.net>
Date: Thu, 16 Jul 2020 00:56:09 -0700
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, DISPATCH WG <dispatch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <99642E4F-047C-4A2B-801C-E4E3FA3265E6@gmail.com>
References: <111A89F4-CBD6-4C63-A45A-C7458E7413FF@mnot.net> <CALGR9oaE8XFdEgOmUWhmP_J89_s-+Xr8hyy5iTZ5SXfkX3aa_g@mail.gmail.com> <B4F7AAFD-BF05-4FF1-A960-827F237C02BB@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/CDv6Y2YFIYy57_ycQDHEo9vxqbk>
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, 16 Jul 2020 07:56:13 -0000

I also see value in recruiting API developers and consumers, but (like Lucas) I struggle to distinguish whether a particular proposal "foo" would be demarcated as HTTP vs. HTTP API.

As a present example, how do we classify the Braid proposal?

    https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-braid-http

On the one hand, we could describe it as "push-update for REST APIs", and then put it into the HTTP API bucket.

But on the other, Braid also applies to browsers and proxies, where it improves caching, reduces network traffic, and allows pages to update automatically without a reload button.  That sounds like core HTTP.

Historical examples could also be interesting.  How do we classify HTTP Live Streaming?

    https://tools.ietf.org/html/rfc8216

This is an API standard, which does not need special browser support.  However, most mobile browsers (but not desktop) now have native implementations for better performance.  Does that make it HTTP core?