W3C home > Mailing lists > Public > public-webcrypto@w3.org > July 2014

RE : [W3C Web Crypto WG] our next call on 21st of July @ 20:UTC (with some votes inside)

From: GALINDO Virginie <Virginie.Galindo@gemalto.com>
Date: Mon, 7 Jul 2014 11:06:35 +0000
To: Brian LaMacchia <bal@microsoft.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
CC: Harry Halpin <hhalpin@w3.org>, Wendy Seltzer <wseltzer@w3.org>
Message-ID: <540E99C53248CE468F6F7702588ABA2AC3659E54@A1GTOEMBXV002.gto.a3c.atos.net>
Hello Brian,

that timing is our usual time for the Web Crypto WG.
The call will be less then one hour, as it will be mainly votes, and no technical debate.
Is there any way for you and the interested people to jump in for this short time ?

Anyone having same problem as Brian to attend the call ?

Regards,
Virginie
________________________________________
De : Brian LaMacchia [bal@microsoft.com]
Date d'envoi : dimanche 6 juillet 2014 19:40
 : GALINDO Virginie; public-webcrypto@w3.org
Cc: Harry Halpin; Wendy Seltzer
Objet : RE: [W3C Web Crypto WG] our next call on 21st of July @ 20:UTC (with  some votes inside)

Hello Virginie,

I believe that the time you have scheduled for the call (20:00 UTC, which would be 16:00 EDT if I have my offsets correct) directly conflicts with the TLS Working Group Monday afternoon session at IETF-90 in Toronto, where similar issues are scheduled to be discussed.  See https://datatracker.ietf.org/meeting/90/agenda.html.  As such, I and possibly many others who have a direct interest in the issues scheduled for the call will not be able to dial in as we'll be at the TLS meeting.  Would it be possible for the W3C to schedule this call at a time that doesn't conflict with IETF-90?

Thanks,

--bal

-----Original Message-----
From: GALINDO Virginie [mailto:Virginie.Galindo@gemalto.com]
Sent: Friday, July 4, 2014 3:39 AM
To: public-webcrypto@w3.org
Cc: Harry Halpin; Wendy Seltzer
Subject: [W3C Web Crypto WG] our next call on 21st of July @ 20:UTC (with some votes inside)

Dear all,

this is a reminder that according to the recent discussions held withing the team [1] and in order to progress on the Last Call exit, we will have a WG call on the 21rst of July @ 20 UTC (or usual timing).

This call will be the opportunity to make a status on the Web Crypto API Last Call process. In particular, we will make formal decision (aka vote) on the 'sensitive' bugs recently highlighted in the team review, which are : 25839 related to curve 25519, 25721 related to key extractability, 25607/18925 related to security considerations.

This call will also treat briefly about the workshop that will be held on 10/11th September in Mountain View [2], related to next Web Crypto WG charter.

If there are any specific topic you would like to adress during that call, please suggest.

Regards,
virginie
chair of the web crypto wg

[1] http://lists.w3.org/Archives/Public/public-webcrypto/2014Jun/0151.html
[2] http://www.w3.org/2012/webcrypto/webcrypto-next-workshop/Overview.html
________________________________
 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.

________________________________
 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.
Received on Monday, 7 July 2014 11:07:49 UTC

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