W3C home > Mailing lists > Public > public-web-security@w3.org > November 2014

[W3C Web Security IG] about Web Crypto rechartering discussion held during Web Crypto F2F meeting

From: GALINDO Virginie <Virginie.Galindo@gemalto.com>
Date: Thu, 6 Nov 2014 12:12:07 +0000
To: "public-web-security@w3.org" <public-web-security@w3.org>
CC: Harry Halpin <hhalpin@w3.org>, Wendy Seltzer <wseltzer@w3.org>
Message-ID: <540E99C53248CE468F6F7702588ABA2AC73C73C9@A1GTOEMBXV003.gto.a3c.atos.net>
Dear all,

A short take away from the W3C Web Crypto WG F2F meeting held last week [1], focusing on the aspects of re-chartering :

-          The actual re-chartering of the Web Crypto WG will not happen before the Web Crypto API is going to Recommendation status. At best, this should happen in January 2014.

-          The current Web Crypto WG participants would prefer to see anything related to accessing services of secure token being developed in a dedicated WG (except cryptographic services, for which it would make sense to do so in the Web Crypto WG)

-          There are best chances that the principle of working in W3C on accessing secure token is endorsed if there are some concrete proposal submitted to W3C, sketching what would a solution look like.

-          Note that from the W3C process point of view, a new Working Group can only be created if at least 20 % of W3C do support the charter (support does not mean join, but means that companies feels it is worth W3C to spend some resources on it).

Hope this help people involved in that topic to define their next steps, to be successful.
Co-chair of web security IG

[1] http://www.w3.org/2014/10/30-crypto-minutes.html#item04
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.
Received on Thursday, 6 November 2014 12:12:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:22 UTC