WEB Crypto WG - Issue Prioritization - 17Sept2012

	A	B	C	D	E
1	date	17/09/2012
2	ISSUE	Status	Description	Domain	Priority
3	ISSUE-36	RAISED	Semantics for key generation versus key derivation	crypto	high
4	ISSUE-3	PENDING REVIEW	Decide whether algorithm discovery is necessary	functional	high
5	ISSUE-38	RAISED	Key initialization and "finalization"	functional	high
6	ISSUE-35	RAISED	Handling of wrap/unwrap operations	functional	high
7	ISSUE-12	RAISED	Should the API distinguish between algorithm and operation parameters?	usability	high
8	ISSUE-14	RAISED	Representation of raw key material	usability	high
9	ISSUE-18	RAISED	Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics?	usability	high
10	ISSUE-29	RAISED	Handling of block encryption modes and padding	crypto	medium
11	ISSUE-31	RAISED	Problems with keys attribute of the Crypto interface	functional	medium
12	ISSUE-17	RAISED	Define the scope and API for custom key attributes	functional	medium
13	ISSUE-6	RAISED	Concern around KeyQueryList being synchronous	functional	medium
14	ISSUE-8	RAISED	Making sure we describe the clean key neutering	functional	medium
15	ISSUE-22	RAISED	Should CryptoOperations be clonable	functional	medium
16	ISSUE-5	RAISED	Public vs. private key pairs -- managing the key pair via a single or multiple handles	usability	medium
17	ISSUE-23	RAISED	Should CryptoOperations and/or Keys support Transferrable semantics?	usability	medium
18	ISSUE-28	RAISED	Short-names for algorithms	usability	medium
19	ISSUE-37	RAISED	Method naming	usability	medium
20	ISSUE-19	RAISED	Does it make sense to have authorized-origin and specific-origin keys	access control
21	ISSUE-2	PENDING REVIEW	How to address pre-provisioned keys and managing ACLs	access control
22	ISSUE-21	RAISED	Requiring Content-Security-Policy	access control
23	ISSUE-26	RAISED	Should key generation be allowed to specify multi-origin shared access	access control
24	ISSUE-27	RAISED	Specification of AES-CTR mode counter bits	crypto
25	ISSUE-10	RAISED	Making sure our API is usable with pure js environement	design
26	ISSUE-24	RAISED	Defining a Synchronous API	design
27	ISSUE-7	RAISED	Deciding if we integrate a high level API in our deliverable	design
28	ISSUE-9	RAISED	what will be the mean to integrate in the API the fact that key usage may need user consent ?	design
29	ISSUE-33	RAISED	Clarify text in section 5.1 with respect to how key tainting is handled with multi-origin scenario	edition
30	ISSUE-32	RAISED	Section 5.2 in API draft should mention use of secure element in the context of key security	edition
31	ISSUE-39	RAISED	Add abort() to the KeyOperation interface	functional
32	ISSUE-25	RAISED	How do we provision Global Unique ID for pre-provisionned symetric keys	key
33	ISSUE-30	RAISED	How does the application know where the key is stored ?	key
34	ISSUE-15	RAISED	Discovering certificates associated with (private) keys	next
35	ISSUE-34	RAISED	Representation of certificates	next
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100