- From: Jim Schaad <ietf@augustcellars.com>
- Date: Sat, 4 Feb 2017 12:35:05 -0800
- To: 'Wendy Seltzer' <wseltzer@w3.org>, <public-webcrypto@w3.org>
Do we know what the status of the CFRG document related to this is? Jim > -----Original Message----- > From: Wendy Seltzer [mailto:wseltzer@w3.org] > Sent: 26 January 2017 08:47 > To: public-webcrypto@w3.org > Subject: Fwd: The W3C Web Cryptography API is a W3C Recommendation > > Thanks to Virginie, MarkW, Ryan, Harry, and all the other contributors, > testers, and implementers of the WebCrypto API. Today, it's a Rec! > > This WG will close at the end of January, per its charter. We will keep the > github repo open for issue-tracking, and plan to discuss errata and updates, > as needed, in the Web Security IG -- feel free to join us there, public-web- > security@w3.org. > > If you're wondering where you'll get your dose of W3C Web standards fun in > the future, I can also recommend the Web Application Security WG and Web > Authentication WG, as well as Web Payments or other upcoming work: > https://www.w3.org/Security/ > > Thanks! > --Wendy > > -------- Forwarded Message -------- > Subject: The W3C Web Cryptography API is a W3C Recommendation > Resent-Date: Thu, 26 Jan 2017 14:18:54 +0000 > Resent-From: w3c-ac-members@w3.org > Date: Thu, 26 Jan 2017 15:18:45 +0100 > From: Coralie Mercier <coralie@w3.org> > To: W3C Members <w3c-ac-forum@w3.org> > CC: chairs@w3.org > > Dear Advisory Committee Representative, > Chairs, > > I am authentically pleased to announce that the W3C Web Cryptography API > is now a W3C Recommendation: > https://www.w3.org/TR/2017/REC-WebCryptoAPI-20170126/ > > This specification describes a JavaScript API for performing basic > cryptographic operations in web applications, such as hashing, signature > generation and verification, and encryption and decryption. > Additionally, it describes an API for applications to generate and/or manage > the keying material necessary to perform these operations. Uses for this API > range from user or service authentication, document or code signing, and the > confidentiality and integrity of communications. > > All Members who responded to the Call for Review [1] of the Proposed > Recommendation showed support (one abstention), with several reviewers > indicating that they produce or expect to produce products that use this > specification. The specification has wide implementation and use helping > Web applications to secure the Open Web Platform. > > Please join us in congratulating the W3C WebCrypto Working Group [2] on > this achievement. > > This announcement follows section 7.1.2 [3] of the W3C Process Document. > > Thank you, > > For Tim Berners-Lee, Director, > Wendy Seltzer, WebCrypto WG Team Contact; Coralie Mercier, Head of W3C > Marketing & Communications > > [1] https://www.w3.org/2002/09/wbs/33280/webcrypto-2016/results > [2] https://www.w3.org/2012/webcrypto/ > [3] https://www.w3.org/2015/Process-20150901/#ACReviewAfter > > -- > Coralie Mercier - W3C Marketing & Communications - http://www.w3.org > mailto:coralie@w3.org +336 4322 0001 > http://www.w3.org/People/CMercier/ > > > > >
Received on Saturday, 4 February 2017 20:35:50 UTC