- From: Ryan Sleevi <sleevi@google.com>
- Date: Wed, 7 Jan 2015 11:43:18 -0800
- To: GALINDO Virginie <Virginie.Galindo@gemalto.com>
- Cc: "public-webcrypto@w3.org" <public-webcrypto@w3.org>, "public-web-security@w3.org" <public-web-security@w3.org>, Wendy Seltzer <wseltzer@w3.org>, Harry Halpin <hhalpin@w3.org>
As noted during the F2F during the 2014 TPAC, it's unlikely we would be able to support such a rechartering. In the goals, only the first goal is something that aligns with our interest. In the scope, we are explicitly not interested in "user managed" storage and "web certificate management". Further, we don't believe this group is the appropriate venue for the discussion of Web Authentication - that would be better for WebApps or WebAppSec. WebAppSec already has proposals for dealing with credentials - http://lists.w3.org/Archives/Public/public-webapps/2014JulSep/0141.html Put differently, for a rechartering, the only effort we'd likely support support is the maintenance and exploration of algorithms. Any other chartering discussions should follow the highly productive workmodes of WebApps and WebAppSecs - that is, concrete, defined proposals being brought forth and holding rechartering discussions in specific and narrow scopes if such proposals have consensus (in particular, from user agents). On Wed, Jan 7, 2015 at 1:48 AM, GALINDO Virginie <Virginie.Galindo@gemalto.com> wrote: > Dear all, > > > > Web Crypto WG charter [1] will end by the end of March. We need to prepare > the next charter of Web Crypto. > > > > As a reminder, the conversation has started on this page : > https://www.w3.org/Security/wiki/IG/webcryptonext_draft_charter > > Feel free to add you ideas and suggestions on the wiki and/or expose your > opinion and question on the public-webcrypto@w3.org or > public-webcrypto-comment@w3.org (for non W3C Web Crypto WG members). > > > > Regards, > > Virginie > > > > [1] http://www.w3.org/2011/11/webcryptography-charter.html > > > > ________________________________ > 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 Wednesday, 7 January 2015 19:50:36 UTC