Re: W3C Web Crypto WG - Shenzhen F2F Take Away

I will try to help for Streams.

Do we have an update on the implementation status/schedule for browsers?

Regards

Aymeric

Le 27/11/2013 15:19, GALINDO Virginie a écrit :
>
> HI all,
>
> In order to make sure all the participants understand where we are on 
> the web crypto side, after our F2F meeting, here is a high level 
> summary of what we did In Shenzhen on 14/15^th of Nov.
>
> -On Web Crypto API
>
> We fixed most of the issues, few of them were kept, with an associated 
> action (see http://www.w3.org/2012/webcrypto/track/actions/open)
>
> Most of the work to improve the spec is now happening in the W3C 
> bugzilla tracker 
> https://www.w3.org/Bugs/Public/buglist.cgi?quicksearch=web%20crypto
>
> The editor need to fix in the spec a lots of wording/clarification, 
> this may be delay by some more emergency work he has to deal with, as 
> such some people volunteered to help, like Mark Watson.
>
> The next step for this spec is to go for Last Call, as soon as this 
> final run will be made. Exact dates will be discussed during our next 
> call.
>
> -On Web Crypto Key Discovery API
>
> The WG decided to postpone for next version the management of 
> retrieving key by origin.
>
> This specification will go for Last Call at the same time as the Web 
> Crypto API.
>
> -On future work
>
> The topics related to certificate, streams integration, multiple key 
> retrieving, ... will be maintained on a wiki 
> http://www.w3.org/2012/webcrypto/wiki/WG_Future_Work
>
> I have allocated a leader for each topic, but anyone can feed the wiki 
> (as usual) with ideas/comments/proposals.
>
> Note that we have decided that high level API was a very-long-term 
> work, as it would require to get feedbacks/usage of the Web Crypto 
> API, before being able to identify the relevant services for such high 
> level api.
>
> -About group life
>
> As the specifications are getting more stable, the editors required to 
> switch smoothly towards a system where decision would be made by mail, 
> rather then during the conference call. As such you will see me more 
> asking for Call For Consensus to adopt technical solution, close issue 
> and other important stuff.
>
> In addition the timing of our call has been moved to 1500 UTC / 8am 
> San Francisco / 11am Boston / 4pm London, staying on a every-two-weeks 
> basis.
>
> We agreed on the principle to meet prior to the IETF march meeting 
> planned in London, provided that we have enough topics to discuss.
>
> Details of that meeting can be found reading the minutes here : day 1 
> http://www.w3.org/2013/11/14-crypto-minutes.html and day 2 
> http://www.w3.org/2013/11/15-crypto-minutes.html
>
> Talk to you next Monday for our call.
>
> Virginie
>
> gemalto
>
>
> ------------------------------------------------------------------------
> 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

-- 
Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms