[mdx] Small change proposed to draft-young-md-query-saml-07

[Cantor, Scott]

On 11/8/17, 3:59 PM, "Tom Scavo" <trscavo at gmail.com> wrote:

> - A responder MAY associate a particular entity with other
> identifiers, including identifiers with the {sha1} syntax.
>
> The latter could be tightened up, I think.

Then I don't get your complaint. That's all the text I proposed was trying to do.

> 2. Extract the 20-byte SourceID value

It in fact is not strictly 20 bytes, as you noted, and we currently blindly send any SourceID we find in the {SHA1} bucket. 

> The use of the {sha1} notation is an unfortunate historical accident.
> SHA-1 is irrelevant to the client.

Right. That's what we were trying to account for with the small tweak.

> Yes, that's my preference but if others want to give the responder
> more flexibility, I'm okay with that as long as the spec is suitably
> rewritten to guide the responder in the right direction.

I feel we did that. I don't know what's significantly wrong with the text I proposed.

I heard you to be proposing we not allow non-SHA1 SourceIDs to be in scope at all and treat the current behavior is just likely to lead to a 404.

-- Scott