- From: Harry Halpin <hhalpin@w3.org>
- Date: Fri, 20 Feb 2015 23:43:57 +0100
- To: Ryan Sleevi <sleevi@google.com>, Richard Barnes <rlb@ipv.sx>
- CC: Israel Hilerio <israelh@microsoft.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>, GALINDO Virginie <Virginie.Galindo@gemalto.com>, Vijay Bharadwaj <Vijay.Bharadwaj@microsoft.com>
On 02/20/2015 11:09 PM, Ryan Sleevi wrote: > On Fri, Feb 20, 2015 at 1:57 PM, Richard Barnes <rlb@ipv.sx> wrote: >> >> >> On Fri, Feb 20, 2015 at 4:46 PM, Israel Hilerio <israelh@microsoft.com> >> wrote: >>> >>> Virginie, >>> >>> >>> >>> Our apologies for being late to the party. Microsoft’s opinion regarding >>> the re-charting of the WebCrypto WG is to focus on the following items: >>> >>> * New algorithms >>> >>> * Extending the APIs to support Streams when the Streams spec is updated >>> by the W3C >> >> >> +1 from the Mozilla side. >> >> To the extent that there is any more work to be done, it is in specifying >> any further algorithms that are necessary. I would caveat, though, that we >> should not take on any deliverables on non-NIST elliptic curves before the >> CFRG process closes. While they are quite a bit behind schedule, they >> appear to be closing in on a solution. >> >> I'm don't have an urgent need for Streams support, but wouldn't object to >> adding the scope. >> >> --Richard > > While it should hopefully come as no surprise and not need saying, > this is exactly our position as well, so a +1 to that :) Congrats for the consensus from all the major browser vendors! That was painless :) It appears the many other items that were brought up may still have quite a lot of interest from members, but we at W3C are also open to looking at other existing WGs or creating new Working Groups. We'll be back in touch with next steps for that early next week. >
Received on Friday, 20 February 2015 22:44:10 UTC