Re: Requesting reviews of draft-vanrein-httpauth-sasl

Paul Vixie <paul@redbarn.org> Thu, 14 May 2020 20:29 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07D453A0CF9 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 14 May 2020 13:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level:
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Zf-5fTne7xld for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 14 May 2020 13:29:38 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (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 6C9B43A0CF1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 14 May 2020 13:29:38 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jZKRK-00054W-2L for ietf-http-wg-dist@listhub.w3.org; Thu, 14 May 2020 20:26:46 +0000
Resent-Date: Thu, 14 May 2020 20:26:46 +0000
Resent-Message-Id: <E1jZKRK-00054W-2L@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <paul@redbarn.org>) id 1jZKRH-00053g-Fj for ietf-http-wg@listhub.w3.org; Thu, 14 May 2020 20:26:43 +0000
Received: from [2001:559:8000:cd::5] (helo=family.redbarn.org) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <paul@redbarn.org>) id 1jZKRF-0002u3-N0 for ietf-http-wg@w3.org; Thu, 14 May 2020 20:26:43 +0000
Received: from linux-9daj.localnet (vixp1.redbarn.org [24.104.150.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 30830B074A for <ietf-http-wg@w3.org>; Thu, 14 May 2020 20:26:27 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: ietf-http-wg@w3.org
Date: Thu, 14 May 2020 20:26:25 +0000
Message-ID: <3041889.qWDYiAHMai@linux-9daj>
Organization: none
In-Reply-To: <217a4fc6-4805-4ee2-bd04-6fbe1d99c35c@nlnet.nl>
References: <B9974B38-6CC7-4979-B08C-ADA6EB22A66A@apple.com> <CABcZeBMD8++_dRtSD704Ymchi2hBxw74Xs+fLSXWj_6WS5d97g@mail.gmail.com> <217a4fc6-4805-4ee2-bd04-6fbe1d99c35c@nlnet.nl>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Received-SPF: pass client-ip=2001:559:8000:cd::5; envelope-from=paul@redbarn.org; helo=family.redbarn.org
X-W3C-Hub-Spam-Status: No, score=-3.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1jZKRF-0002u3-N0 67b0a7cf7f0d4e5aa054895ea775bf4e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Requesting reviews of draft-vanrein-httpauth-sasl
Archived-At: <https://www.w3.org/mid/3041889.qWDYiAHMai@linux-9daj>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37622
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>

On Thursday, 14 May 2020 17:00:37 UTC Michiel Leenaars wrote:
> Hi Eric,
> 
> > "Arguably" is doing a lot of work here, as CDNs have already
> > evolved well beyond this (cf. edge compute).
> 
> that would be companies providing CDN also (or actually) providing cloud
> services on their distributed infastructure, rather than an actual delivery
> network: an intermediate (but passive) cache layer with high availability,
> for static assets. As you rightly point out, in the case of outsourced
> cloud services any such infrastructure would in fact be the origin for all
> intents and purposes - even if some data is fetched once in a while from
> some back end.

i don't think your attempt to define CDN is relevant. the companies selling 
things under that umbrella are either leading or following the market, rather 
than consulting a dictionary to find our what business they are in. see here:

https://www.fastly.com/edge-cloud-platform

as far as i know all players in the CDN market offer similar services, except 
perhaps a commercial publication services provider whose primary liability 
shield comes from saying that they are "just a proxy" and that they don't host 
anything. if so that can be expected to change, because "content" is no longer 
primarily static or passive and that trend will accelerate.

whether it's done with docker images or python applets doesn't matter. the 
nature of content has changed, and the nature of content delivery networks has 
changed with it. no protocol or platform or business which refuses or ignores 
this change will make a new world-line. this is the future we're in. http 
authentication will have to account for this, but whether that happens inside 
the IETF or outside in the market is a choice this WG can still make.

-- 
Paul