W3C home > Mailing lists > Public > public-webcrypto@w3.org > August 2012

RE: New Editor's Draft published

From: Ali Asad <Asad.Ali@gemalto.com>
Date: Mon, 20 Aug 2012 20:10:22 +0200
To: Ryan Sleevi <sleevi@google.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Message-ID: <821D566D81EF6F4F830409E0BD3B1022C41E0BC981@ABSEXCFWP01.gemalto.com>
Hi Ryan,

Thanks for these updates. Just one comment, all the links [1] to [8] at the bottom of your email go to the same place - end of the Editor's Draft page. Something for the editors to look into perhaps.

Regards,
--- asad

-----Original Message-----
From: Ryan Sleevi [mailto:sleevi@google.com] 
Sent: Monday, August 20, 2012 9:29 AM
To: public-webcrypto@w3.org
Subject: New Editor's Draft published

A new version has been published at
http://www.w3.org/2012/webcrypto/WebCryptoAPI/ in anticipation to moving towards FPWD. All core API functionality should minimally have IDL specified.

Key changes in this version (r1.15) from the previous major update (r1.13)
 - Attempt to fully specify an algorithm (RSAES-PKCS1-v1_5) as an example of how the algorithm specifications may look [1]
 - Attempt to specify the basic state machine for CryptoOperation in normative terms
   - Added an abort method to abort in-progress operations [3]
 - Add in DH [4], spec out SHA-1/SHA-2 [5]
 - Various updates to the WebIDL based on Web API Cookbook recommendations
 - Add interfaces for key (generation, derivation, import, export) based on Vijay's proposed interfaces [6]
 - Add simple KeyStorage interface for origin-generated and previously origin-authorized keys [7]
 - Formalize the registration for a number of algorithms [8]
   - Specify their well known name
   - Specify their expected algorithm parameters
   - Specify the contents of result
   - Clamp parameter inputs to cause errors to be thrown when necessary
 - Remove various TODOs
   - Such as notes for DSA or for Concat KDF; judge demand

Based on my understanding of the chairs' positions on the necessary progression towards FPWD, we should have the core interfaces spec'd here. That isn't to say that they can't all wildly change, but please focus on making sure that there is consensus to move forward with this draft and that it accurately represents the discussions from the WG mailing list and conference calls.

Cheers and looking forward to discussing these changes, Ryan

[1] http://www.w3.org/2012/webcrypto/WebCryptoAPI/#rsaes-pkcs1
[2] http://www.w3.org/2012/webcrypto/WebCryptoAPI/#CryptoOperation-states
[3] http://www.w3.org/2012/webcrypto/WebCryptoAPI/#dfn-CryptoOperation-method-abort
[4] http://www.w3.org/2012/webcrypto/WebCryptoAPI/#dh
[5] http://www.w3.org/2012/webcrypto/WebCryptoAPI/#sha
[6] http://www.w3.org/2012/webcrypto/WebCryptoAPI/#KeyOperation-interface
[7] http://www.w3.org/2012/webcrypto/WebCryptoAPI/#dfn-KeyStorage
[8] http://www.w3.org/2012/webcrypto/WebCryptoAPI/#algorithms
Received on Monday, 20 August 2012 18:10:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 August 2012 18:10:47 GMT