ACTION-1 |
closed |
To help collect use-cases around key isolation |
Mitch Zollinger |
2012-07-02 |
Web Cryptography Use-cases |
ACTION-2 |
closed |
to start a wikipage to start collecting the use-cases for secondary features |
Nadim Kobeissi |
2012-07-02 |
Web Cryptography Use-cases |
ACTION-3 |
closed |
Update the API proposal to reflect support for short names |
Ryan Sleevi |
2012-07-09 |
|
ACTION-4 |
closed |
Sleevi to come back with a description of naming algorithms. |
Ryan Sleevi |
2012-07-09 |
|
ACTION-5 |
closed |
A discussion to have a proposal for mapping strings to algorithm ojbects |
Ryan Sleevi |
2012-07-09 |
|
ACTION-6 |
closed |
to add to spec having an attribute for making private key material accessible with default being private key material being inaccessible |
David Dahl |
2012-07-09 |
Web Cryptography API |
ACTION-7 |
closed |
a proposal for mapping strings (JOSE IETF work) to algorithm objects |
Ryan Sleevi |
2012-07-09 |
Web Cryptography API |
ACTION-8 |
closed |
and sdurbha to draft a minimal set of mandatory algorithms, ideally compatible with the strawman proposal from rsleevi |
David Rogers |
2012-07-09 |
Web Cryptography API |
ACTION-9 |
closed |
to produce a proposal for adding some key identification/handling methods to the API |
David Dahl |
2012-07-09 |
Web Cryptography API |
ACTION-10 |
closed |
Sleevi to propose a strong definition of what "extractable" / "non-extractable" means |
Ryan Sleevi |
2012-07-23 |
|
ACTION-11 |
closed |
wtc to work with channy to improve the use cases document |
Wan-Teh Chang |
2012-07-23 |
Web Cryptography Use-cases |
ACTION-12 |
closed |
to clarify scope of API regarding key storage and smart card use |
Jim Davenport |
2012-07-23 |
Web Cryptography API |
ACTION-13 |
closed |
And Arun to add missing use-cases |
Wan-Teh Chang |
2012-09-10 |
Web Cryptography Use-cases |
ACTION-14 |
closed |
Change naming scheme to use a "createX" approach rather than just "X" |
Ryan Sleevi |
2012-09-10 |
ISSUE-37 |
ACTION-15 |
closed |
Insert in "right place" a description of high-level example |
David Dahl |
2012-08-20 |
|
ACTION-16 |
closed |
Add the key query mechanism to editors draft, checking in with ddahl's edit |
Ryan Sleevi |
2012-08-20 |
|
ACTION-17 |
closed |
Review key generation and propose a way for user agents to expose unique IDs as first class |
Mitch Zollinger |
2012-08-20 |
Global Unique ID |
ACTION-18 |
closed |
Sleevi to propose a method for key generation that fully specifies the intended algorithm usage (eg: RSA-PSS), not just the algorithm family (eg: RSA) |
Ryan Sleevi |
2012-08-20 |
|
ACTION-19 |
closed |
Return with report on XMLSec PAG |
Wendy Seltzer |
2012-08-27 |
|
ACTION-20 |
closed |
Write a straw-man proposal re: incorporating "recommended" table and description of test suite |
Harry Halpin |
2012-08-01 |
MUST or SHOULD |
ACTION-21 |
closed |
With other browser makers, to do research/outreach on contacts and public keys |
David Dahl |
2012-08-20 |
|
ACTION-22 |
closed |
And cjkula to describe key import/export functionality |
Vijay Bharadwaj |
2012-08-01 |
|
ACTION-23 |
closed |
Find out status of getRandomValues in HTML5 |
Harry Halpin |
2012-08-01 |
|
ACTION-24 |
closed |
Add section to the draft on random number generation |
Wan-Teh Chang |
2012-08-20 |
|
ACTION-25 |
closed |
Formalize that when we have a key handle, operations on the key should apply on the source of the key |
Wan-Teh Chang |
2012-08-01 |
|
ACTION-26 |
closed |
Review state of the art on symmetric key properties |
Vijay Bharadwaj |
2012-08-20 |
|
ACTION-27 |
closed |
Add primary use cases to the specification |
Arun Ranganathan |
2012-08-01 |
Web Cryptography API |
ACTION-28 |
closed |
Follow up with Facebook on signed code use case |
Christopher Kula |
2012-08-01 |
Web Cryptography API |
ACTION-29 |
closed |
Follow up on tools with Jarred and/or others |
Harry Halpin |
2012-09-10 |
|
ACTION-30 |
closed |
Update the editor's draft regarding ISSUE-11, based on harry's suggestion to add informative suggestion |
Ryan Sleevi |
2012-08-13 |
storage attribute |
ACTION-31 |
closed |
Storage of key and parameters in different locations |
Ryan Sleevi |
2012-08-27 |
Web Cryptography API |
ACTION-32 |
closed |
Propose text/API to the mailing list to address ISSUE-14 |
Ryan Sleevi |
2012-08-20 |
ISSUE-14 |
ACTION-33 |
closed |
text proposal for key pair handling |
Ryan Sleevi |
2012-08-27 |
Keypair |
ACTION-34 |
closed |
Add explicit language to clarify that Key object attributes are persistent to keys. the key.id is consistent between browsing contexts |
Ryan Sleevi |
2012-08-27 |
Web Cryptography API |
ACTION-35 |
closed |
Talk to adrian bateman re IE implementation of getRandomValues |
Harry Halpin |
2012-08-27 |
|
ACTION-36 |
closed |
key exchange with DH |
Mark Watson |
2012-08-28 |
Web Cryptography API |
ACTION-37 |
closed |
Rename SHA-2-* to just SHA-* |
Wan-Teh Chang |
2012-08-29 |
Web Cryptography API |
ACTION-38 |
closed |
Write some non-normative text about pre-shared keys |
Mark Watson |
2012-09-03 |
|
ACTION-39 |
closed |
Sample code |
Asad Ali |
2012-09-03 |
Web Cryptography API |
ACTION-40 |
closed |
Propose text for scope section about smart card |
Asad Ali |
2012-09-04 |
Web Cryptography API |
ACTION-41 |
closed |
Propose text for key neutering |
Ryan Sleevi |
2012-09-04 |
key neutering |
ACTION-42 |
closed |
Normative description of the algorithm for key generation, derivation, importing, and exporting |
Ryan Sleevi |
2012-09-14 |
Web Cryptography API |
ACTION-43 |
closed |
Write some sample code |
David Dahl |
2012-09-13 |
Web Cryptography API |
ACTION-44 |
closed |
addition of 'netflix use cases' in the draft API in section 2 |
Ryan Sleevi |
2012-09-12 |
Web Cryptography Use-cases |
ACTION-45 |
closed |
And wseltzer to move the Editors Draft to TR space and communicate to the chairs@w3.org, the Director, and Comms Team over the FPWD publication |
Harry Halpin |
2012-09-17 |
|
ACTION-46 |
closed |
Create use-case document space for Arun |
Harry Halpin |
2012-09-17 |
|
ACTION-47 |
closed |
[admin] Questionnaire on new time slot for conf calls |
Virginie GALINDO |
2012-09-25 |
|
ACTION-48 |
closed |
FPWD communication - inform IETF JOSE WG about publication |
Michael Jones |
2012-09-25 |
|
ACTION-49 |
closed |
FPWG communication - inform CFRJ |
Zooko Wilcox-O'Hearn |
2012-09-25 |
|
ACTION-50 |
closed |
Issue Structuration - reshape issue domains to include key/access control/attribute |
Virginie GALINDO |
2012-09-25 |
|
ACTION-51 |
closed |
Building value proposition about Web Crypto API |
Virginie GALINDO |
2012-09-26 |
|
ACTION-52 |
closed |
Add text as regards security considerations for algorithms |
Ryan Sleevi |
2012-10-01 |
|
ACTION-53 |
closed |
Write some text around CSP and Web Security model |
Harry Halpin |
2012-10-01 |
|
ACTION-55 |
closed |
Draft security considerations |
David Dahl |
2012-10-15 |
|
ACTION-56 |
closed |
Write proposal for ISSUE-27 |
Wan-Teh Chang |
2012-10-15 |
aes ctr |
ACTION-57 |
closed |
Fix broken API link |
Ryan Sleevi |
2012-10-29 |
|
ACTION-58 |
closed |
And Mark to work on proposal for ISSUE-12 |
Wan-Teh Chang |
2012-11-12 |
usability for Web Crypto API |
ACTION-59 |
closed |
Update the formats to remove PKCS#1 and add SPKI |
Ryan Sleevi |
2012-11-08 |
usability for Web Crypto API |
ACTION-60 |
closed |
Specify text that makes it clear we do not specify any particular Web storage mechanism, but we use a Web storage mechanism rather than an independent key storage object |
Ryan Sleevi |
2012-11-08 |
|
ACTION-61 |
closed |
Determine if a generic algorithm procedure is necessary for his use-case |
Mountie Lee |
2012-11-08 |
|
ACTION-62 |
closed |
(and others) to bring back functions and a draft WebIDL for the higher-level API |
David Dahl |
2012-12-03 |
|
ACTION-63 |
closed |
And tlr to handle any concerns from public and communications about WG's work |
Virginie GALINDO |
2012-11-09 |
|
ACTION-65 |
closed |
JOSE liaison about the possibility of new format to be defined |
Michael Jones |
2012-11-19 |
|
ACTION-66 |
closed |
define use cases for wrap/unwrap feature |
Mark Watson |
2012-11-19 |
wrapping |
ACTION-67 |
closed |
Legal aspects with respect to national directives |
Virginie GALINDO |
2012-12-19 |
Web Cryptography API |
ACTION-68 |
closed |
Public Key discovery on website |
David Dahl |
2012-11-19 |
Web Cryptography Use-cases |
ACTION-69 |
closed |
Alignment of API and Use case specifications |
Arun Ranganathan |
2012-11-19 |
Web Cryptography Use-cases |
ACTION-70 |
closed |
Propose language on relation between WebCryptoAPI and use cases |
Virginie GALINDO |
2012-12-17 |
|
ACTION-71 |
closed |
Update Use Cases to conform to Pub Rules |
Arun Ranganathan |
2012-12-24 |
|
ACTION-72 |
closed |
Update ED to Pub Rules for next WD |
Ryan Sleevi |
2012-12-24 |
|
ACTION-74 |
closed |
Contact PING over privacy |
Harry Halpin |
2013-01-28 |
|
ACTION-75 |
closed |
And wseltzer to prepare extension request for 6 months |
Harry Halpin |
2013-02-11 |
|
ACTION-77 |
closed |
Make sure Microsoft can make Wednesday morning |
Harry Halpin |
2013-04-22 |
|
ACTION-78 |
closed |
Write informative text recommending CSP |
Ryan Sleevi |
2013-04-30 |
ISSUE-21 |
ACTION-79 |
closed |
Write up a use case for the origin sharing |
Mountie Lee |
2013-04-30 |
|
ACTION-80 |
closed |
Write up use case for the pre-provisioned key discovery use case |
Karen Lu |
2013-04-30 |
|
ACTION-81 |
closed |
Describe we're not storing key material itself in IDB |
Ryan Sleevi |
2013-04-30 |
|
ACTION-84 |
closed |
Vgb and jimsch to discuss key generation/derivation/agreement |
Richard Barnes |
2013-05-21 |
derivation |
ACTION-85 |
closed |
And vgb to propose a means for auto-generating IVs in 3 weeks |
Richard Barnes |
2013-05-21 |
|
ACTION-87 |
closed |
Update result to be ArrayBuffer than ArrayBufferView |
Ryan Sleevi |
2013-04-30 |
|
ACTION-88 |
closed |
Review syntactic sugar overloads for taking (ArrayBuffer and ArrayBufferView) |
Ryan Sleevi |
2013-04-30 |
|
ACTION-90 |
closed |
Add in wrap/unwrap as "feature at risk" to low-level |
Ryan Sleevi |
2013-05-01 |
|
ACTION-92 |
closed |
Add JOSE use case |
Arun Ranganathan |
2013-05-01 |
|
ACTION-93 |
closed |
Add caveats showing that web crypto WG is only addressing a subset of some use cases |
Arun Ranganathan |
2013-05-01 |
|
ACTION-94 |
closed |
Add BrowserID use case to use cases document |
Arun Ranganathan |
2013-05-01 |
|
ACTION-95 |
closed |
Document a cross-origin use case for webcrypto |
Arun Ranganathan |
2013-05-01 |
|
ACTION-98 |
closed |
Get review of dictionary/WebIDL problem from TAG and/or WebApps |
Ryan Sleevi |
2013-05-20 |
usability for Web Crypto API |
ACTION-99 |
closed |
Get review of ArrayBuffer/ArrayBufferView problem from TAG and/or WebApps |
Ryan Sleevi |
2013-05-20 |
usability for Web Crypto API |
ACTION-100 |
closed |
creation of a wiki section dedicated to test activity |
Virginie GALINDO |
2013-07-14 |
|
ACTION-101 |
closed |
Publish new editor's draft due June 3 |
Ryan Sleevi |
2013-06-03 |
Web Cryptography API |
ACTION-102 |
closed |
And wendy/harry to get clarity on status of futures |
Virginie GALINDO |
2013-06-03 |
|
ACTION-103 |
closed |
Ping Privacy Interest Group to put Key Discovery in radar before we go to next publication |
Harry Halpin |
2013-06-03 |
|
ACTION-107 |
closed |
With markw to make sure it goes through WD via W3C TR |
Harry Halpin |
2013-07-29 |
|
ACTION-108 |
closed |
Clarify that use case document will be a note from the Web Crypto WG |
Arun Ranganathan |
2013-07-29 |
Web Cryptography Use-cases |
ACTION-113 |
closed |
And wseltzer to ping systeam to push Use-cases and Key Discovery out |
Harry Halpin |
2013-08-12 |
|
ACTION-136 |
closed |
Clarify the editorship of Web Crypto API spec |
Virginie GALINDO |
2013-12-23 |
Web Cryptography API |
ACTION-137 |
closed |
Strawman proposal prioritizing bugs to address for the next version of Web Crypto API |
Virginie GALINDO |
2013-12-23 |
|