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 27581 - Wording: Algorithm names must be unique when compared case-insensitively
Summary: Wording: Algorithm names must be unique when compared case-insensitively
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:38 UTC by Eric Roman
Modified: 2016-05-23 23:59 UTC (History)
3 users (show)

See Also:

Attachments

Description Eric Roman 2014-12-11 22:38:53 UTC 
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.
Comment 1 jimsch 2016-03-09 06:44:33 UTC 
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
Comment 2 Mark Watson 2016-05-23 23:59:32 UTC 
Moved to https://github.com/w3c/webcrypto/issues/55