This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27580 - "case sensitive" --> "case insensitive"
Summary: "case sensitive" --> "case insensitive"
Status: RESOLVED MOVED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-11 22:34 UTC by Eric Roman
Modified: 2016-05-23 23:58 UTC (History)
3 users (show)

See Also:

Attachments

Description Eric Roman 2014-12-11 22:34:10 UTC 
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.
Comment 1 jimsch 2016-03-09 06:19:04 UTC 
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.
Comment 2 jimsch 2016-03-09 06:45:16 UTC 
I missed the difference between a WebCrypt algorithm identifier and a JWK algorithm identifier - ignore my last comment.
Comment 3 Mark Watson 2016-05-23 23:58:50 UTC 
Moved to https://github.com/w3c/webcrypto/issues/54