Per-Entity Metadata Working Group

["Walter Forbes Hoehn (wassa)" <>]

> On Aug 4, 2016, at 9:07 AM, Tom Scavo 
> <>
>  wrote:
> 
> On Thu, Aug 4, 2016 at 9:53 AM, Cantor, Scott 
> <>
>  wrote:
>>> Open this directory structure for access via rsync, Dropbox, OwnCloud,
>>> 'you name it' to sync the signed files to campuses operating their own
>>> local MDQ server to get independent from the centrally operated MDQ. No
>>> need for HTTP proxies, just for local MDQ servers at the campuses.
>> 
>> Right, but how many campuses will want to do that? How many will bother?
> 
> If our experience with Duo Security is any indicator, there is a
> significant fraction of deployments that care about outages of cloud
> services. This has been discussed (with the community) many times. The
> same concerns will surface in the case of per-entity metadata
> distribution.

With even the most rudimentary caching in place, MDQ clients will be 
considerably more tolerant of infrastructure hiccups than Duo clients, which 
typically initiate multiple REST calls for every authentication.

-WFH