27580 2014-12-11 22:34:10 +0000 "case sensitive" --> "case insensitive" 2016-05-23 23:58:50 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC Linux RESOLVED MOVED P2 normal --- 1 ericroman sleevi ietf public-webcrypto watsonm oldest_to_newest 116178 0 ericroman 2014-12-11 22:34:10 +0000 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. 125392 1 ietf 2016-03-09 06:19:04 +0000 This is the language used for JSON Web Algorithm to address the same question Names may not match other registered names in a case-insensitive manner unless the Designated Experts state that there is a compelling reason to allow an exception. Algorithm names are supposed to be compared in a case-sensitive manner so this would, strictly speaking, be a necessary update. On the other hand, it will reduce potential errors to make this statement. If there is a requirement that all algorithm are registered in the JSON Web Algorithm registry then there is no need to make this change as the DE for that registry will enforce this requirement. I don't think at this point in time we need to make this change as it is indirectly done by the JWK and JWA specs. 125395 2 ietf 2016-03-09 06:45:16 +0000 I missed the difference between a WebCrypt algorithm identifier and a JWK algorithm identifier - ignore my last comment. 126514 3 watsonm 2016-05-23 23:58:50 +0000 Moved to https://github.com/w3c/webcrypto/issues/54