W3C Web Crypto WG - about the NUMS/25519 curves integration in Web Crypto API

Hello Web Crypto participants,

Following our call last week [1], I have listed the different ideas/directions that were raised about the way to proceed on the integration of NUMS and 25519 curves, as discussed in bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=25839

** Two possible options to handle NUMS and 25519 curves integration
OPTION 1 :
- We can decide to have an extension for NUMS and already have an editor for it
- We can decide to have an extension for curves 25519 and have a potential draft with an editor coming on 10th of august
- We can decide to have that/those extension(s) mandatory in the future browser profile
Or
OPTION 2 :
- We can decide ‘not to choose between extension and main spec’ but decide on the principle to develop the NUMS/curve 25519 descriptions and put it into the spec once it is tested and proven it is available

** Other requirements :
- We have to stay synchronized with IETF/CFRG - TLS requirements, which may require new algorithms → this is in favor of delaying the decision, expecting IETF decision
- Learning loop : We have to decide how to make our spec extensible → this is favor to make early choice and beta test extension addition

I would like to have your views on the preferred path to progress, option 1 or option 2.
If you have another option, feel free to suggest.

Note that we have a call scheduled next Monday 11th of August to discuss that question, but early opinion are helping to make calls efficient.

Regards,
Virginie
Chair of the web crypto WG


[1] http://lists.w3.org/Archives/Public/public-webcrypto/2014Jul/0144.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.

Received on Monday, 4 August 2014 13:41:13 UTC