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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/07/2014 01:06 PM, GALINDO Virginie wrote:
> 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 ?

Quite a few people (including W3C staff) may be at IETF, not just
Brian. I'd be happy to move call out a week.

    cheers,
       harry

> 
> 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.
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTupwdAAoJEPgwUoSfMzqcASEP/3JXJDOAmajjQ5Likl+eO3nO
1zPgZ9MybGLmTgaqUN8VVIWcNJeyYq1WQLPj4W4JrzE8BrYbthVPAvomZWnLvmlY
itTp0HXPr1b+8zih8mpVJ2KgeCtbhX4qoPCsWJ6SVat+PvoO+j/ZIz4FCfVhjgGq
a3LJymCS6UxFPY1Oei0lmHNtMPfe+cUyWEAgQdsbMN0M9BmWK9A0N/sYuuMHYfue
vY6egWyfU+N6I+SOPhhCAK2iNEBAT/K+Z5R/VDGqhTA3DulI0PKydMBQl0XNQfQP
BqjDT881OKr2Ptyyql5VA+9sxuoH9af3eDCesw9/igLEU9arXU93dEDp6SMS2Bwv
2tKdRdL2YP+mcePdsh6u5XeDyG58gXmAwHXK34UF7D5qtxWdLiKYqfTZzsfHBOyo
Ld1dwcCV9OdE/xCvKA3R761fatgw9p1moeQNh77Oev10zeBM7aaR+fq3SS79UQNp
2QgGf873R/fazA3arHoD15O94Nz48Yc4IdcXLXKuDa5fUkQS08APL/UGqza4bsJ2
VBKYwEy6NEUXAZ056C77vSCTyr1MAqlnDRtIeX8AXZLtbDbw9czVlJZQ7CuLhjRw
c/DuGZkvwR9vKeSIGv8rw1osUXQhR69LL0BaVr9pTgKRDtyvcuzt0PQzrFfmYcRY
iNifsDw9ytjlRJcp/Soy
=m7Lu
-----END PGP SIGNATURE-----

Received on Monday, 7 July 2014 13:09:59 UTC