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 22548 - Specify the "normalization" rules for reflecting keyUsage
Summary: Specify the "normalization" rules for reflecting keyUsage
Status: RESOLVED FIXED
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: Mark Watson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-03 01:07 UTC by Eric Roman
Modified: 2014-02-28 01:44 UTC (History)
4 users (show)

See Also:

Attachments

Description Eric Roman 2013-07-03 01:07:47 UTC 
Key creations methods take as input a KeyUsage[].
This KeyUsage[] is also reflected back in the created Key.keyUsage.

==> What normalization steps is the user agent allowed to perform on the reflected Key.keyUsage object?

It would convenient if neither order, nor duplicates had to be preserved, so internally a set could be used (for instance a bitfield).
Comment 1 Ryan Sleevi 2013-11-14 07:30:22 UTC 
From Shenzhen F2F, MichaelH: Will specify that usages are sorted (in some form) for syntactic sugar purposes.
Comment 2 Mark Watson 2014-02-28 01:23:28 UTC 
I propose to specify that what is reflected is de-duplicated and sorted in the order the usages are listed in the list of recognized key usage algorithms.
Comment 3 Mark Watson 2014-02-28 01:44:58 UTC 
Changeset ca494eeb8ddf