Futures/Promises update from W3C
W3C Web Crypto WG - second tentative for our F2F meeting - please answer questionnaire
W3C Web Crypto - about next F2F meeting on 26/27 July in Berlin
W3C Web Crypto WG - adhoc call on Web Crypto Key Discovery - 25/May/2013
ACTION-86: Make a proposal for an explicit auto generation token for IV
W3C Web Crypto WG - our next adhoc call on monday 27th of May @ 20:00 UTC
W3C Web Crypto WG - attending next F2F meeting in Berlin ?
W3C Web Crypto WG - PROPOSAL to close action-87
W3C Web Crypto WG - minutes of of the call - 20 May 2013
W3C Web Crypto WG - take away from our call - 20th of May 2013
W3C Web Crypto WG - new editor's draft for Web Crypto API
[ACTION-89] On the nature of Streams
ACTION-84: Finishing support for key derivation/key agreement
- RE: ACTION-84: Finishing support for key derivation/key agreement
W3C Web Crypto WG - Survey : do you plan to attend a F2F meeting in Berlin this summer ?
W3C Web Crypto WG - regular conf cal next monday @ 20:UTC
Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- RE: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- RE: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- RE: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
- Re: Follow-up. Re: Use case: Authenticate using eID
May 14thKey Derivation/Key Agreement Telecon minutes
W3C Web Crypto WG - adhoc call today @ 20:00 UTC on key lifecycle
Dates and location for WebCrypto meeting in Berlin
AES-GCM Algorithm is missing tag properties for input params and result value
- Re: AES-GCM Algorithm is missing tag properties for input params and result value
- RE: AES-GCM Algorithm is missing tag properties for input params and result value
- RE: AES-GCM Algorithm is missing tag properties for input params and result value
- RE: AES-GCM Algorithm is missing tag properties for input params and result value
High-level API meetings?
Re: ISSUE-26 is expecting proposal or will be postponed
Minutes of May 6th Telecon
Re: Use case: Authenticate using eID
W3C Web Crypto WG - adhoc call on Web Crypto Key Discovery API
W3C Web Crypto WG - adhoc call on Key agreement/generation/derivation
W3C Web Crypto WG - W3C testing methodology
W3C Web Crypto WG - 2 additionnal calls in May
Additional use cases
Re: ISSUE-35 - Wrap/Unwrap - Why JOSE?
Meeting today: Agenda for Telecon Monday May 6th 20:00 GMT
W3C Web Crypto WG - agenda for our call on monday 6th of May @20:00 UTC (today!)
Take the W3C Brand Survey (through 5 May)
RE: Web Crypto Spec Feedback on Dictionaries as return type properties
Web Crypto Spec Feedback on Dictionaries as return type properties
RE: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams
- Re: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams
- RE: Web Crypto Spec Updates for ArrayBufferView, ArrayBuffer, and Streams