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

[W3C Web Crypto WG] - Take Away from 18th of June 2012 meeting

From: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
Date: Wed, 20 Jun 2012 14:50:12 +0200
To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
CC: "hhalpin@w3.org" <hhalpin@w3.org>, "wseltzer@w3.org" <wseltzer@w3.org>
Message-ID: <1126F161F6F1B24FABD92B850CAFBD6E0171CE61413A@CROEXCFWP04.gemalto.com>
Dear all,

Based on our minutes [1], here is my take away from our Mondays call, highlighting next steps we should take care of, and action we agreed on. Thanks to Emily for scribing !

Note that next call is scheduled the 2nd of july 2012 @ 19:00 UTC, next week call is cancelled for chair-holidays reasons.




Chair of Web Cryptography WG

[1] http://www.w3.org/2012/06/18-crypto-minutes.html

----- Take away from 18 June 2012 call by Virginie G ------

** About use cases drafted in our wiki

Update is available under http://www.w3.org/2012/webcrypto/wiki/Use_Cases

== NEXT STEP ==> Participants to make sure their use cases are addressed.


** About draft API

A) About the general scope of our API

In our previous call we decided that the draft API we would concentrate on the low level API, in the boundary of primary features as mentioned in our charter. During this call we discussed the area that should be covered by the low level API.

== DECISION ==>  the following area will be covered : key identification, key usage (crypto operations to be performed with), key management (key generation, usage and deletion), discovery mechanism (platform capabilities algo).

B) About security framework and requirements

It has been suggested that we maintain a list of security/privacy points we should take care of, and  a list of security requirements to draw the security environment we are presupposing in our work.

== NEXT STEP ==> Call for volunteer to maintain a wiki page ?

C) Discovery mechanism proposed in github https://github.com/daviddahl/web-crypto-ideas/blob/master/algorithm-discovery.js

== NEXT STEP ==> Participants to comment this proposal and offer by mail or on github amendments if needed.

Note : the special use case of having a dynamic capabilities on the platform (e.g. a new hardware token is plugged on the device, offering new algorithm capabilities) has been discussed. The consensus is to make sure the discovery mechanism takes this special case into account, if this is not possible, it will be kept as a secondary features.  Any volunteer to write down the use case ?

D) Key usage

A contribution from Ryan has been presented http://lists.w3.org/Archives/Public/public-webcrypto/2012Jun/0117.html

== NEXT STEP ==> Participants to comment this proposal by mail

E) Key Management

Is the next big topic to treat

== NEXT STEP ==> Editors/Participants to propose mechanism.

F) About the dates for issuing our First Public Working Draft

== DECISION ==> The first Public Draft for Comment will be delivered in Summer 2012, after our F2F, and will contain open issues.

** About the Group Life

F2F in Summer will be held on 24/25 July in Mountain view.

== NEXT STEP ==> Participants to register to David Dahl and W3C/chair/host to deliver details for logistics.

Received on Wednesday, 20 June 2012 12:50:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:10 UTC