W3C home > Mailing lists > Public > public-webcrypto@w3.org > January 2013

Re: W3C Web Crypto WG - take away from the 7th of Jan conf call

From: Richard Barnes <rbarnes@bbn.com>
Date: Tue, 8 Jan 2013 11:17:33 -0500
Cc: "'public-webcrypto@w3.org'" <public-webcrypto@w3.org>, Wendy Seltzer <wseltzer@w3.org>, Harry Halpin <hhalpin@w3.org>
Message-Id: <C371230C-2134-49BA-B54A-ED2153E9114E@bbn.com>
To: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
One small edit:
"Richard from BBN [1]" -> "Richard from BBN [5]"
"[5] http://polycrypt.net"


On Jan 8, 2013, at 6:49 AM, GALINDO Virginie <Virginie.GALINDO@gemalto.com> wrote:

> Dear all,
>  
> Here is a short take away from our discussions yesterday. This does not replace the official minutes that are available under :http://www.w3.org/2013/01/07-crypto-minutes.html  (thank you so much Ryan for scribing *and* contributing).
>  
> -          Status about our deliveries
> As per 17th of dec resolutions, the 3 documents (usecases [1] , web crypto API [2] and web crypto key discovery [3]) are going to Working Draft on the 8th of January.
> The high level API will be discussed during our next conference call.
> The secondary features are not addressed yet, but Mountie mentioned that it would be good to allocate priorities to it and start working. This will be discussed in our next conf call.
>  
> -          Discussion about implementations
> The implementation is a key mean to progress in the development of the Web Crypto API. At the moment there is one known implementation shared by Richard from BBN [1]. Mark W mentioned that Netflix was working on a plugin. Other implementers need more time to give a date where more feedbacks will be available to progress on the Web Crypto API.
> This information is important to establish our roadmap and forecast about Last Call date.
>  
> -          Discussion about the main issues to address
> Editor mentioned that major impacting topics were : import/export, wrap/unwrap, cloning. Those features are complex enough to block our delivery, and to such point we may take decision to keep them or not on our scope.
> Mike Johns (selfissued) confirmed that IETF JOSE WG would address our request to define JavaScript Object Notation (JSON) representations of private keys and symmetric keys (see recent JSON WG activity under http://tools.ietf.org/wg/jose/ )
> There was a contribution by Netflix about wrap/unwrap that will be discussed in our next conference call (see history underhttp://www.w3.org/2012/webcrypto/track/issues/35 ).
>  
> -          Discussion about the next F2F meeting
> The next meeting will be located in US. Ideal dates for meeting are 26/27/28th of March. It is suggested to switch by few weeks the meeting and have it in April. Another doodle has been created to see if and when we could meet in April. Doodle has been created to survey : http://doodle.com/rn6bgzg4a44m5ig9
> -          AOB
> A crypto meeting is planned this week in Stanford https://crypto.stanford.edu/RealWorldCrypto/program.php some of the WG participants will attend and may advert our recent specifications.
>  
> Our next conference call is planned on the 21st of Jan, @15:00 UTC on our usual channels.
>  
> Regards,
> Virginie
> Gemalto
> Chair of the Web Crypto WG
>  
> [1] use case http://dvcs.w3.org/hg/webcrypto-usecases/raw-file/tip/Overview.html
> [2] web crypto key discovery https://dvcs.w3.org/hg/webcrypto-keydiscovery/raw-file/tip/Overview.html
> [3] web crypto API http://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html
> [4] http://lists.w3.org/Archives/Public/public-webcrypto/2013Jan/0003.html
Received on Tuesday, 8 January 2013 16:18:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:14 UTC