W3C Web Crypto WG - 27th of January take away

Dear all,

This is a take away of the WG conference call held on the 27th of January.


-          We reviewed the bug list and proposals from mark to resolve it http://lists.w3.org/Archives/Public/public-webcrypto/2014Jan/0039.html. Note that a new version of the specification has been issued on on 27th of January with some bug fixed https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html

-          We discussed the timeline to go to Last Call and drafted the following milestones : Spec ready for Last Call published on the 24th of February, decision by the WG to actually go for LC on the 10th of march

-          We decided to take the opportunity of the STRINT and IETF meetings to organize a F2F meeting in London on the 27th of February, which agenda will focus on Future Work. *Note* : as reminded by Wendy, this cannot be a formal meeting, as such, our discussions will not lead to any formal decision or orientation for the WG.

-          We discussed briefly the hardware token workshop, I suggested to enlarge a bit the scope to trusted element in general (without precluding their hardware or software nature). A strawman proposal will be issued soon.

The actual minutes of the call are available under http://www.w3.org/2014/01/27-crypto-minutes.html

Note that our editors do need your view on the bug resolutions, so please pay attention to their call for comments. In order to make sure everyone follows the bug resolution, the mailing list will be soon copied for any move on that matter.

Virginie
Chair of the web crypto wg


[please ignore the following confidential statement]


________________________________
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