W3C Web Crypto WG - asian call take awayo 10th of february

Hi all,

A short take of our synchronization call with asia at 9:00 UTC today. We had a one hour discussion with mountie (paygate), sangrae (etri), kishan (tiphone), harry (W3C). As the W3C bridge was not set up, we moved to another bridge and did not have logs of the conversation. As such, here is my brief take away.

Discussions:
We discussed the status of the Web Crypto API based on recent editors mail.
We mentioned that any new topic should be addressed during the informal F2F meeting on 27th of February in London and/or after the 10Th of March which is the expected date for sending the specifications to Last Call.
Mountie and Sangrae mentioned their needs for 1) clarifying the key storage definition (currently left to the implementers in the specification) and 2) allowing the scenario of a site A delivering a key to be used by a site B (also known as exception to the same origin policy).  In that case, it is expected that the user would be in charge of accepting this exception. Prior to sending requirements to the Web Crypto WG, it was recommended by Harry to have a deep analysis of CORS in order to see how it could map to device key/certificate management.
Harry reminded that WWW2014 will be held in Korea, and a session dedicated to the next crypto in W3C could be scheduled. This could be a good place to advert this kind of need.
We discussed briefly the possibility to have a workshop in Sept in Washington DC to discuss hardware tokens (or broader scope, to be defined with the WG).

Action :
Mountie and Sangrae to document the wiki related to the certificate management with use cases and functional requirements
Harry to follow up on the WWW2014 session

Regards,
Virginie
Gemalto
chair of web crypto wg


________________________________
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