On 28/07/16 16:31, "nygren@gmail.com<mailto:nygren@gmail.com> on behalf of Erik Nygren" <nygren@gmail.com<mailto:nygren@gmail.com> on behalf of erik@nygren.org<mailto:erik@nygren.org>> wrote:
I also think that we shouldn't refer to "CDN" in this scenario as much as referring to delegating between a server acting as an authoritative origin and a collection of servers at a lower trust level. (In some deployment scenarios, the former might be a CDN and the latter might be either a different trust tier of CDN nodes or federated-but-less-trusted partners.)
+1. We should not restrict the discussions (or mechanisms) to existing CDN deployments- using CDN's as concrete examples can be useful but we must not limit the discussion to these cases.
For instance, the case when the same actor is running the origin (primary) as well as the secondary server but on someone else site and/or could platform are also relevant.
The specific blind caching with a configured proxy cache is a well-defined use-case, but the others have many different ways to implement that trying to standardize something now before there has been more experience with implementations and business models seems like asking for trouble (and is something that some of us may be less interested in than in defining common underlying mechanisms and affordances to allow developing technologies in this area).
Agreed. Getting the basic HTTP mechanisms in place should be the initial focus. But discussing different use cases may be useful when identifying requirements on the various mechanisms.
Regards
Göran