- From: Paul Vixie <paul@redbarn.org>
- Date: Thu, 14 May 2020 20:26:25 +0000
- To: ietf-http-wg@w3.org
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
Received on Thursday, 14 May 2020 20:26:43 UTC