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

[W3C Web Crypto WG] - Take Away from 21st of May 2012 meeting

From: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
Date: Tue, 22 May 2012 16:35:00 +0200
To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Message-ID: <1126F161F6F1B24FABD92B850CAFBD6E0115340A8A50@CROEXCFWP04.gemalto.com>
Dear all,

Based on our minutes, here is my take away from our call yesterday, highlighting actions we should take care of. 
Note that next call is scheduled the 4 Of June @ 19:00 UTC. 


Chair of Web Cryptography WG

----- Take away from 21 May 2012 call by Virginie G ------

** About writing down our primary usecases
Survey about the API, designed by Wan The and David has been sent over the mailing list http://lists.w3.org/Archives/Public/public-webcrypto/2012May/0101.html 
== NEXT STEP ==> Participants to review/comment the survey. 

** About reviewing the draft API 

A) algorithm to be supported by the API
It has been decided that list of algorithms to be supported would be similar to the ones IETF is referencing and this list will be integrated in the API. Specific technology will be removed on a case by case basis, on the basis of strong facts. 
== NEXT STEP ==> Editors to integrate algorithms in the draft API.

B) discovery mechanism
We had discussions about i) the need or not to leave all algorithms optional or to define a core set of mandatory algorithms, ii) the need to know which type of API we want to design (high level or low level). A suggestion was made that in case we have both high level and low level, we may have low level API associated with a discovery mechanism and a high level API based on specific mandatory algorithms. The concern of agility and cryptography evolution has been highlighted and it has been discussed that we could address agility by a serious maintenance of our specifications. 
My guess, as chair : we will end up with a two levels API (high and low), I would recommend people to start thinking about this kind of architecture. 
NEXT STEP ==> Wait the result of the survey. 
C) random generation
Random generation is addressed elsewhere in HTML domain (see http://wiki.whatwg.org/wiki/Crypto). 
Two concerns about redesigning this feature in our API are raised : (1) we should not duplicate features in W3C specifications, (2) implementations of this crypto already exist in several Browsers. 
== NEXT STEP ==> Participants to list/remind the good reasons for not referencing the HTML existing feature. 

** About the Group Life

Calls : RESOLUTION : the regular call will be held every Mondays @ 19:00 UTC  (unless we discover it does not work).  

Next F2F : a Doodle will be soon in your mailboxes to choose the best 2 days for our F2F either during the weeks starting on the 28th of July or 13th of August 2012
== NEXT STEP ==> Participants to answer the doodle, choosing the 2 consecutives dates that would better suit you. 

Received on Tuesday, 22 May 2012 14:35:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:01:01 UTC