Per-Entity Metadata Working Group

[Scott Koranda <>]

Hello,

Some InCommon Participants would like to be able to configure
their Microsoft ADFS service(s) to consume InCommon metadata 
for specific entities using HTTPS as the transport and the TLS
trust model.

An InCommon MDQ service that used HTTPS (in addition to HTTP)
would facilitate that request.

The above is one (1) argument in favor of adding HTTPS
transport and TLS trust for the InCommon MDQ service.

Are there other arguments in favor?

My understanding is that the InCommon TAC in particular has
had objections in the past to serving any InCommon metadata
that *relies* on the TLS trust model.

Can someone familiar with that objection (Scott C or Tom S or
Nick R or ?) provide more details, or correct my understanding
if I am wrong?

What other objections are there to serving InCommon metadata
using the TLS trust model?

Thanks,

Scott K