W3C home > Mailing lists > Public > public-webcrypto@w3.org > September 2012

Re: [W3C Web Crypto WG] FPWD Web Crypto API - available

From: Harry Halpin <hhalpin@w3.org>
Date: Thu, 13 Sep 2012 21:01:04 +0200
Message-ID: <50522D70.10603@w3.org>
To: Wendy Seltzer <wseltzer@w3.org>
CC: David Dahl <ddahl@mozilla.com>, Axel Nennker <Axel.Nennker@telekom.de>, Ryan Sleevi <sleevi@google.com>, Virginie GALINDO <Virginie.GALINDO@gemalto.com>, public-webcrypto@w3.org
On 09/13/2012 08:56 PM, Wendy Seltzer wrote:
> Thanks David and Axel,
>
> Working Drafts are static after publication, so changes will go into the
> Editor's Draft (as David has already done) and go out to /TR/ in the
> next public Working Draft. We can publish new Working Drafts whenever we
> feel there's been significant progress, no less frequently than a
> 3-month heartbeat.
In general its better to publish WDs after the first WD has a round of 
substantial comments, so it's OK to leave that in as a egg. In fact, it 
will be empirically interesting to see how many other people catch that 
particular bug!

As soon as it gets published on the W3C homepage, please broadcast as 
far as possible. A few high-profile security blogs would help, as there 
has been some interesting arguments over JS Webcrypto for the last year. 
I'll help by forwarding to Ron Rivest to forward out to the academic 
community and various folks at NIST. The wider the review, the earlier, 
the better!

>
> --Wendy
>
> On 09/13/2012 02:20 PM, David Dahl wrote:
>> I fixed this mistake in http://www.w3.org/2012/webcrypto/WebCryptoAPI/ - what is the proper way to migrate it into the WD?
>>
>> David
>>
>> ----- Original Message -----
>> From: "David Dahl" <ddahl@mozilla.com>
>> To: "Axel Nennker" <Axel.Nennker@telekom.de>, hhalpin@w3.org
>> Cc: wseltzer@w3.org, "Virginie GALINDO" <Virginie.GALINDO@gemalto.com>, public-webcrypto@w3.org, "Ryan Sleevi" <sleevi@google.com>
>> Sent: Thursday, September 13, 2012 12:12:55 PM
>> Subject: Re: [W3C Web Crypto WG] FPWD Web Crypto API - available
>>
>> Axel:
>>
>> Yes, you are correct. My mistake.
>>
>> Harry:
>>
>> Once I fix that in our repo, what is the process to update the published version?
>>
>> David
>>
>>
>> ----- Original Message -----
>> From: "Axel Nennker" <Axel.Nennker@telekom.de>
>> To: "Virginie GALINDO" <Virginie.GALINDO@gemalto.com>, public-webcrypto@w3.org
>> Cc: wseltzer@w3.org, hhalpin@w3.org
>> Sent: Thursday, September 13, 2012 8:57:33 AM
>> Subject: RE: [W3C Web Crypto WG] FPWD Web Crypto API - available
>>
>> In 25.2 Key Storage
>>
>> var encryptionKey = window.keys.getKeyById("78966b83-b003-46ac-8122-3771e9d7f78");
>>
>>
>>
>> // This key is no longer needed, I should remove it:
>>
>> window.keys.removeKeyById(encryptionKey.id);
>>
>>
>>
>> var otherEncryptionKey = window.keys.getKeyById("5edbeebe-bbbf-4d60-9846-8bbdb81e3215");
>>
>>
>>
>> shouldn't that read
>>
>> var encryptionKey = window.crypto.keys.getKeyById("78966b83-b003-46ac-8122-3771e9d7f78");
>>
>>
>>
>> // This key is no longer needed, I should remove it:
>>
>> window.crypto.keys.removeKeyById(encryptionKey.id);
>>
>>
>>
>> var otherEncryptionKey = window.crypto.keys.getKeyById("5edbeebe-bbbf-4d60-9846-8bbdb81e3215");
>>
>> instead?
>>
>>
>>
>> Axel
>>
>>
>>
>> -----Original Message-----
>> From: GALINDO Virginie [mailto:Virginie.GALINDO@gemalto.com]
>> Sent: Thursday, September 13, 2012 3:28 PM
>> To: public-webcrypto@w3.org
>> Cc: Wendy Seltzer; Harry Halpin
>> Subject: [W3C Web Crypto WG] FPWD Web Crypto API - available
>>
>>
>>
>> Dear all,
>>
>> The Web Crypto API is now available under http://www.w3.org/TR/WebCryptoAPI/.
>>
>> Regards,
>>
>> Virginie
>>
>>
>>
>> -----Original Message-----
>>
>> From: GALINDO Virginie
>>
>> Sent: jeudi 13 septembre 2012 07:18
>>
>> To: public-webcrypto@w3.org
>>
>> Cc: Wendy Seltzer; Harry Halpin
>>
>> Subject: [W3C Web Crypto WG] Request transition for FPWD on Web Crypto API - approved
>>
>>
>>
>> Dear all,
>>
>>
>>
>> This is to inform you that the request for transition to FPWD has been approved by the domain team leader (Thomas Roessler). Next step is the migration under http://www.w3.org/TR/WebCryptoAPI/ official link. Will keep you informed.
>>
>>
>>
>>
>>
>> Regards,
>>
>> Virginie, gemalto
>>
>> Happy Chair of Web Crypto WG
>>
>>
>>
>>
>
Received on Thursday, 13 September 2012 19:01:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 September 2012 19:01:21 GMT