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

Re: New Editor's Draft published

From: Harry Halpin <hhalpin@w3.org>
Date: Mon, 20 Aug 2012 16:46:54 +0200
Message-ID: <50324DDE.9050603@w3.org>
To: Ryan Sleevi <sleevi@google.com>
CC: public-webcrypto@w3.org
Congrats! During the telecon today, it would make sense for you to go 
over the changes, and then we need to give at least 1 week for review by 
the WG and then get formal consensus on its publication on our meeting 
on 27th of August so we can then at earliest probably aim for 
publication on August 30th.

    cheers,
         harry

On 08/20/2012 04:28 PM, Ryan Sleevi wrote:
> 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 14:47:02 GMT

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