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

RE: Random numbers

From: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
Date: Wed, 16 May 2012 15:11:11 +0200
To: Wan-Teh Chang <wtc@google.com>, Jarred Nicholls <jarred@webkit.org>, David Dahl <ddahl@mozilla.com>
CC: Philip Gladstone <pgladsto@cisco.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Message-ID: <1126F161F6F1B24FABD92B850CAFBD6E0102BDF05248@CROEXCFWP04.gemalto.com>
Jarred, Wan-Teh, David

I have been under the Crypto work managed in the WHATWG, which redirects to W3C repositories, and found the same usual suspects behind this feature (e.g. our kind editors ;-). So I have a question about the way we would like the group to manage this random generation - if demonstrated that it is needed by the usecases. 

Could you please clarify the status of this proposal and recommend the next steps (e.g. remove this item from the HTML domain, or state that it is now endorsed elsewhere in the Web Crypto API, ...). I would like to make sure we do not have multiplication of API across W3C. 

Regards,
Virginie


-----Original Message-----
From: Wan-Teh Chang [mailto:wtc@google.com] 
Sent: Tuesday, May 15, 2012 8:31 PM
To: Jarred Nicholls
Cc: Philip Gladstone; public-webcrypto@w3.org
Subject: Re: Random numbers

On Tue, May 15, 2012 at 9:28 AM, Jarred Nicholls <jarred@webkit.org> wrote:
>
> Note that this almost directly correlates with the future decision of 
> the level of API this WG is aiming to build (low, medium, high) and 
> the use cases it aims to satisfy, i.e., if crypto RNG is a necessity 
> for an accepted use case.  Perhaps the next step is to weigh in on or 
> create use cases that provide more points towards deciding on the API level.

Crypto RNG is an important part of a crypto API.  I think this need is already satisfied by window.crypto.getRandomValues.

Wan-Teh
Received on Wednesday, 16 May 2012 13:11:50 UTC

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