Re: [jose] Stephen Farrell's Discuss on draft-ietf-jose-json-web-key-33: (with DISCUSS and COMMENT)

[Stephen Farrell <[e-mail]>]

On 08/10/14 01:47, Mike Jones wrote:
> The real rule is "always case sensitive unless otherwise specified".
> I think the right fix is to be clear on that point.  Stephen and
> Barry, can I proceed on that basis and have you review the proposed
> edits?

I'm not clear what edits you are proposing but I do think that
submitting an updated draft is fine and we can look at that and
see how it maps to the various discuss/comment points more
easily than fully process this many threads in parallel.

That said, I don't agree that the "rule" you state above is
universal - messy as it may be, reality requires dealing with
both case sensitive and case insensitive identifiers as well
as i18n for string comparisons. In the case of key ids, I
don't think there's a generic i18n issue, but there is a real
issue that DNS names will be used as part of key ids. That
real issue cannot be wished away via specification language
no matter how smart or subtle so any updated text that does
not have some level of messiness will unfortunately likely
not be fit for purpose. (If however your edits are pretty
much along the lines of the text previously discussed, then
as I've said, I'll be fine to clear the discuss.)

S.