- From: Mark Watson <watsonm@netflix.com>
- Date: Wed, 29 Jan 2014 14:58:59 -0800
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: Ryan Sleevi <sleevi@google.com>, "public-webcrypto-comments@w3.org" <public-webcrypto-comments@w3.org>
- Message-ID: <CAEnTvdA+WzhTCc2MmZdPFe8+itnL=m0vfwKisGR7vN1WAhDwXw@mail.gmail.com>
Melvin, I would suggest you raise a bug to track this request. The link for raising bugs is at the front of the WebCrypto document. ...Mark On Wed, Jan 29, 2014 at 2:42 PM, Melvin Carvalho <melvincarvalho@gmail.com>wrote: > > > > On 15 December 2013 20:53, Ryan Sleevi <sleevi@google.com> wrote: > >> Also, please do not cross-post to non-W3C lists. Removed the bitcoin-dev >> list for those who wish to reply. >> > > Hi Ryan, apologies for cross posting, and thanks for the reply! > > I've been super excited about web crypto even since I saw David Dahl's > demo at TPAC, 2 years ago. I think that at the time this group's charter > was written, crypto currencies were relatively unknown. However, over the > last year they have exploded in popularity. "Bitcoin" was one of the top > 100 searches globally last year, and even has made it into the Oxford > English Dictionary. > > It would be fantastic if this curve were able to make it into the > registry, and User Agents were given an opportunity to implement. The Free > Software community could perhaps offer some code, where that applies. > > I understand that it would be a feature at risk, thank you for at least > taking the time to give it some consideration. Please let me know if > there's anything I can do that might help facilitate this. > > >> Cheers >> On Dec 15, 2013 10:10 AM, "Melvin Carvalho" <melvincarvalho@gmail.com> >> wrote: >> >>> Harry and David suggested I send a message to this group. I was >>> wondering if the crypto group may consider adding support for >>> *secp256k1* in the browser Named Curve dictionary. >>> >>> http://www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dictionary >>> >>> enum NamedCurve { >>> // NIST recommended curve P-256, also known as secp256r1. >>> "P-256", >>> // NIST recommended curve P-384, also known as secp384r1. >>> "P-384", >>> // NIST recommended curve P-521, also known as secp521r1. >>> "P-521" >>> }; >>> >>> Over the last year, there has been a significant increase in deployment >>> for this curve. It's used in bitcoin and many other crypto currencies. >>> Bitcoin deployment now numbers in the millions of users and hundreds of >>> companies. There are also free software implementations in most >>> languages. >>> >>> For more background on Koblitz curve used by bitcoin see: >>> >>> https://bitcointalk.org/?topic=2699.0 >>> >>> I'm aware that the API tends to expose what's existing in NSS, but, >>> imho, if it were possible to add support for this curve would be a great >>> step to help to many people that already work with crypto currencies in the >>> browser. >>> >> >
Received on Wednesday, 29 January 2014 22:59:28 UTC