- From: Anders Rundgren <anders.rundgren@telia.com>
- Date: Thu, 28 Mar 2013 18:45:54 +0100
- To: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
- CC: Aymeric Vitte <vitteaymeric@gmail.com>, Mountie Lee <mountie.lee@mw2.or.kr>, Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>, "public-webcrypto-comments@w3.org" <public-webcrypto-comments@w3.org>, Harry Halpin <hhalpin@w3.org>
On 2013-03-28 17:55, GALINDO Virginie wrote: > Mountie, Nick, Aymeric, > > Some time will be allocated during our San Jose F2F meeting to presen > a draft for this feature. That would be great if you could make it > available a little bit before the F2F. Please do but don't forget to mention how it relates to existing certificates including such distributed in hard tokens like in the EU and Asia. Anders > > Regards, > Virginie > > -----Original Message----- > From: Aymeric Vitte [mailto:vitteaymeric@gmail.com] > Sent: lundi 4 mars 2013 14:52 > To: Harry Halpin > Cc: Nick Van den Bleeken; Mountie Lee; public-webcrypto-comments@w3.org > Subject: Re: draft for certificate management > > > Le 04/03/2013 13:04, Harry Halpin a écrit : >> Also, when writing the spec try to determine if you could use the >> low-level API to build what parts, and what other parts would need >> some level of access to browser internals. Some features could be done >> in a library on top of the Crypto API I hope. > > Of course!!! It has to use/extend the low-level API, the example I am giving can only be a real world example facilitator. > > Regards > > Aymeric > > -- > jCore > Email : avitte@jcore.fr > iAnonym : http://www.ianonym.com > node-Tor : https://www.github.com/Ayms/node-Tor > GitHub : https://www.github.com/Ayms > Web : www.jcore.fr > Webble : www.webble.it > Extract Widget Mobile : www.extractwidget.com BlimpMe! : www.blimpme.com > > > >
Received on Thursday, 28 March 2013 17:46:36 UTC