> This brings me back around to wondering why just saying that Key > ID values are case sensitive strings is not enough, and leaving it up > to applications how to choose the contents of those case-sensitive > strings?
Yes, that's fine, if that's adequate for the situation. Remember that this all came from what's in the documents now, with statements such as this (from JWT, Sections 5.1 and 5.2): While media type names are not case-sensitive, it is RECOMMENDED that "JWT" always be spelled using uppercase characters for compatibility with legacy implementations. Use of this Header Parameter is OPTIONAL. That violates the "always case sensitive" rule, and requires that you deal with comparisons and/or normalization. If you just say that everything is case sensitive, or REQUIRE those strings to be case-normalized, that addresses the problem. Barry _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
