Per-Entity Metadata Working Group

[Tom Scavo <>]

On Tue, Aug 2, 2016 at 11:03 AM, Chris Phillips
<>
 wrote:
>
> Can someone weigh in on the qualities REQUIRED of an MDQ consumer and the
> place on the wiki they exist?
> E.g. 'Consumer MUST be able to retrieve MDQ ack/nack of a record in X ms'

AFAIK, no one has voiced such a requirement. In any case, I'm not sure
how valuable such a requirement would be. It's unrealistic to think a
server will never fail. The question is: what happens when it *does*
fail.

> 'Consumer MUST respect validUntil timestamp and cache MDQ response until
> then'

No, you're confusing validUntil with cacheDuration, but in any case
this is purely a client-side issue. Both Shibboleth and SSP respect
these XML attributes AFAIK. Others clients may be lacking, I don't
know.

Btw, InCommon metadata has never had an explicit cacheDuration value.
Should the MDQ server include one? A realistic value would be 24
hours. Not sure if this is useful or not.

> Federation operators
> around the globe operate this now and MDQ 'answers'  are not very different
> from serving up a metadata aggregate at all — are they?

I claim they are definitely different (but at least Scott thinks otherwise).

Tom