Per-Entity Metadata Working Group

["Cantor, Scott" <>]

On 9/14/16, 2:33 PM, 
"
 on behalf of Tom Scavo" 
<
 on behalf of 
>
 wrote:

> Well, I can answer the latter question definitively...per-entity
> metadata will produced once per business day, in conjunction with our
> current metadata signing process. When we push newly signed aggregates
> to md.incommon.org (around 3:30 pm ET), we will also push newly signed
> entities to mdq.incommon.org at more-or-less the same time.

I think the more relevant question is whether we have a policy of emergency 
signing in the face of a key compromise. If so, the refresh policy would be 
driven by that more than the routine case.

I know I refresh every 4 hours now, but that's mostly historical and because 
the HTTP conditional GETs make it free for me to do so.

Anyway, you get my point: you want cacheDuration to drive the consumers to 
check at the interval you want to be able to get a revocation change made.

-- Scott