- From: Harry Halpin <hhalpin@w3.org>
- Date: Thu, 20 Nov 2014 01:37:11 +0100
- To: Trevor Perrin <trevp@trevp.net>
- CC: Mark Watson <watsonm@netflix.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>, GALINDO Virginie <Virginie.GALINDO@gemalto.com>, Ryan Sleevi <sleevi@google.com>
Virginie,
Can you do a call for consensus (with usual 2 week waiting time) for
Curve 25519 to go to Working Draft?
I'll install an Editor's Draft in W3C space and do the boiler-plate
work, but it would be good if the WG had any concerns/bugs to voice them
now.
I think the general extensibility mechanism and the addition of Curve
25519 extension spec means I think we've resolved as "LATER" the Curve
25519 bug in the Web Cryptography API's move to Candidate Recommendation.
cheers,
harry
On 11/19/2014 07:23 PM, Trevor Perrin wrote:
> On Mon, Nov 17, 2014 at 11:07 AM, Harry Halpin <hhalpin@w3.org> wrote:
>>
>> 1) Elliptic Curve bugs re NUMS and Curve 25519
>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839
>>
>> We should probably add this Editor's Note to the 3.1.1
>>
>> "We expect the WebCrypto specification to support whatever alternative
>> named curves outside of the NIST elliptic curves are recommended by CFRG
>> either in the main specification or as an extension specification."
>>
>> We also need to put Trevor's Draft in W3C Space and probably at same
>> time as CR as a Working Draft and list it in extensions here:
>>
>> I've pinged him about this, I imagine it can happen by end of the week.
>
> In response to above:
>
> I'd be happy to see this draft advance as a Working Draft, and to let
> the staff contact work on adding any appropriate boilerplate,
> publication date, etc. (I'll be too busy / travelling this week and
> the next to do such work myself).
>
> Trevor
>
Received on Thursday, 20 November 2014 00:37:21 UTC