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

Virginie,

I think it's entirely reasonable to consider this BUG open even if
everything else in the spec was ready to go to REC track.

There are several possible resolutions:
- Keep the bug open, so that any time someone goes to file a bug, they
presumably see the existing bugs, and don't file a dupe.
- Close the bug as WONTFIX/Future Work, since it indicates something that
is not likely to make it to the spec sent to LCWD/CR.
- Close the bug as WONTFIX/Invalid, since no spec action was received prior
to the deadline imposed for NUMS. Seems arbitrarily capricious, but an
action that would be valid none the less.

My own preference is that for all the bugs we acknowledge as things we'd
"like to have in the future", we keep them open in some state. This at
least signals to the community that there are known-ponies-and-bikesheds in
the list of things people want to have. But we do differentiate them from
bugs we "need to fix before CR/REC".


On Fri, Jul 25, 2014 at 11:47 PM, GALINDO Virginie <
Virginie.Galindo@gemalto.com> wrote:

>  Ryan,
> Do you suggest we keep open theat bug until the actual curve 25519 contribution is received (independantly from our decision to integrate or not NUMS) ?
> Virginie
>
> ---- Ryan Sleevi a écrit ----
>
>
>  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>
> 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> 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.
>