W3C home > Mailing lists > Public > public-webcrypto@w3.org > March 2014

W3C Web Crypto WG - take away from our 10th of March call

From: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
Date: Mon, 17 Mar 2014 18:11:43 +0100
To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
CC: Harry Halpin <hhalpin@w3.org>, Wendy Seltzer <wseltzer@w3.org>
Message-ID: <239D7A53E5B17B4BB20795A7977613A40207D8ED4198@CROEXCFWP04.gemalto.com>
Dear all,

Here is a (late and) short take away from our call, held last week.

-          We discussed the way to move forward to Last Call for our Web Crypto API specification.

-          After collecting questions, we realized that one feature was still under discussion in the working group, for which a bug reference is 24963, related to the type of return expected form the export key operation (see  https://www.w3.org/Bugs/Public/show_bug.cgi?id=24963). Several ideas were expressed about the fact that this feature was required prior to go for last call or not.

-          After looking at different scenario, the participants decided were in consensus to go for Last Call, provided that a note calling for developers feedback on the export . The period for Last Call was decided to be 8 weeks in order to allow the editors and working group participants to ping the crypto experts, in order to make efficient reviews.

This take away does not replace the official minutes which are available here http://www.w3.org/2014/03/10-crypto-minutes.html (thanks harry for scribing).



Technical Marketing & Innovation
Mob: +33 6 13 23 20 03
La Vigie - Avenue du Jujubier - ZI Athelia IV
13 705 La Ciotat Cedex - France


This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus

(image/jpeg attachment: image001.jpg)

(image/jpeg attachment: image002.jpg)

Received on Monday, 17 March 2014 17:12:08 UTC

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