This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section "18.2.1. Naming" says that: "Every cryptographic algorithm defined for use with the Web Cryptography API MUST have a unique name, referred to as its recognized algorithm name, such that no other specification defines the same case-sensitive string for use with the Web Cryptography API." The use of "case-sensitive" seems misleading here. Because algorithm names are compared in a case-insensitive manner, all recognized names must be unique when compared case-insensitively.
The place where it says case-insensitive is in the normalization algorithm in 18.4.4. I would say that the correct answer is to fix this and make it a case-sensitive comparison at this location. As thing currently stand it is case sensitive in some locations (algorithm normalization) and case insensitive in other locations (the alg field of a JWK). Making it consistent seems to be a good idea
Moved to https://github.com/w3c/webcrypto/issues/55