RE: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519

Hi Brian,
Sorry if I was not clear. As mentionned by Ryan, i did not mean to ignore your contribution.  My point here is to identify the status of the bug, once NUMS discussion done, as no contribution for curves 25519 has been received.
Virginie

---- Brian LaMacchia a écrit ----


Thanks.  Virginie’s mail implied summary resolution of the bug and a change to the proposed resolutions that she sent out earlier, which is why I was confused.

--bal

From: Ryan Sleevi [mailto:sleevi@google.com]
Sent: Friday, July 25, 2014 6:27 PM
To: Brian LaMacchia
Cc: GALINDO Virginie; Wendy Seltzer; public-webcrypto@w3.org; Harry Halpin
Subject: RE: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519


Absolutely, Brian. Please don't let my response regarding Curve25519 detract from the work on NUMS.

I think Virginie still plans to send out a proposal for resolving the NUMS aspect, and in particular if and how its integrated into the spec, since you did indeed submit by the deadline specified.

Its exactly why I think Curve 25519 should proceed independently, since no such submission for it was made for it.
On Jul 25, 2014 4:15 PM, "Brian LaMacchia" <bal@microsoft.com<mailto:bal@microsoft.com>> wrote:
I object to summary resolution of this bug as WONTFIX at this time.  This bug concerns adding new elliptic curves to the W3C spec, including both Curve25519 and the NUMS curves.  Virginie set out a process on 6/25 (see [1])  giving the respective proponents of the new curves until July 11 to submit proposed changes to the spec to include the curves.  I submitted my proposal for modifying the spec to include support for the NUMS curves on time per Virginie’s process.  The fact that none of the Curve25519 supporters chose to do the work to propose spec modifications by the July 11 deadline Virginie specified in no way invalidates my own timely submission of the NUMS curves changes.

                                                                                                --bal

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839#c39

From: Ryan Sleevi [mailto:sleevi@google.com<mailto:sleevi@google.com>]
Sent: Friday, July 25, 2014 6:53 PM
To: GALINDO Virginie
Cc: Wendy Seltzer; Harry Halpin; public-webcrypto@w3.org<mailto:public-webcrypto@w3.org>
Subject: Re: [W3C Web Crypto WG] suggested resolution for bug 25839 on curve25519


Well, Trevor has expressed interest in proposing as a separate spec. It doesn't seem like WONTFIX fully captures the sentiment that it can proceed independently, and producing such a spec is necessary to close out some of our extensibility issues...
On Jul 25, 2014 3:49 PM, "GALINDO Virginie" <Virginie.Galindo@gemalto.com<mailto:Virginie.Galindo@gemalto.com>> wrote:

Indeed, thanks Ryan. This means that bug will be a wontfix,  as it may only be answered by adding algorithms not initially required by bug reviewers.  Give me some time (and sleep) to rephrase the bug resolution proposals.

Virginie



>From my mobile



---- Ryan Sleevi a écrit ----




On Fri, Jul 25, 2014 at 3:17 PM, GALINDO Virginie <Virginie.Galindo@gemalto.com<mailto:Virginie.Galindo@gemalto.com>> wrote:
Dear all,


Here is some possible resolutions for the bug 25839 on curve25519 https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839
As required, Microsoft provided on time a contribution aiming to describe curve 25519 in the main specification of Web Crypto API [1]. As announced by the chair [2], the Working Group participants will be asked to vote for the possible following resolutions in order to close that bug.

Virginie,

Microsoft did not provide text for Curve 25519. They provided it for NUMS curves. No support for Curve25519 is described in the Microsoft proposal.



Possible resolutions :

Resolution one : The WG resolves the bug by closing it and endorsing the curve description provided by Microsoft, as such, in the main W3C Web Crypto API.

Resolution two : The WG resolves the bug by closing it and endorsing the curve description provided by Microsoft, in a dedicated extension, which will have its own track to become a Recommendation.



These resolutions will be submitted to WG participants vote during our call next Monday as announced over the mailing list [3].



Regards,

Virginie



[1] http://lists.w3.org/Archives/Public/public-webcrypto/2014Jul/0041.html

[2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839#c42

[3]  http://lists.w3.org/Archives/Public/public-webcrypto/2014Jul/0016.html


(please ignore statement below)

________________________________
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.
________________________________
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.