Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.48 as permitted sender)
	client-ip=209.85.215.48; envelope-from=melvincarvalho@gmail.com;
	helo=mail-la0-f48.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAKaEYhLH+5E0cpF1NN4VOG0Rpg7AE6aUGPG++8RO6TupndL4Dg@mail.gmail.com>
References: <CAKaEYhLH+5E0cpF1NN4VOG0Rpg7AE6aUGPG++8RO6TupndL4Dg@mail.gmail.com>
Date: Wed, 29 May 2013 14:14:20 +0200
Message-ID: <CAKaEYhKrdt61Osih+3KCdM4HLw-CRd5kN5CeT1M23Jc=y478wA@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c268a64b83f904ddda525f
Subject: Re: [Bitcoin-development] WebCryto standard to support secp256r1
	but not secp256k1
Precedence: list

--001a11c268a64b83f904ddda525f
Content-Type: text/plain; charset=ISO-8859-1

On 7 May 2013 12:18, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

> Looking at the proposed native crypto browser support (should arrive in
> the next year)
>
> http://www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dictionary
>
> We see:
>
> 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"
> };
>
> I wonder if we might be able to get bitcoin's curve in there
>
> For more background on Koblitz curve used by bitcoin see:
>
> https://bitcointalk.org/?topic=2699.0
>

Hi All

I enuired about this and got the following reply, from the chair of the
crypto group:

[[
Just email public-webcrypto-comments@w3.org. It's a public list. Do
definitely mention your use-cases!

I think there's issues of whether NSS etc. already support it. I think the
answer here is "no" but David can clarify. The goal is not to get browser
vendors to write new crypto code, but to expose the crypto code that
already exists.

We still have an open issue about whether "experimental" registry for
identifiers for say, new curves that aren't in the core spec, will be
maintained. So, maybe if browsers don't support it today, it's always
possible they might want to support it tomorrow given Bitcoin's growth.
]]

Please let me know if anyone has a use case for ecdsa in the browser let me
know.

Or if anyone would like to write to the public list that's fine

Otherwise I'll just fire off a mail and see what they come back with ...

--001a11c268a64b83f904ddda525f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 7 May 2013 12:18, Melvin Carvalho <span dir=3D"ltr">&lt;<a href=
=3D"mailto:melvincarvalho@gmail.com" target=3D"_blank">melvincarvalho@gmail=
.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Looking =
at the proposed native crypto browser support (should arrive in the next ye=
ar)<br>
<div><br><a href=3D"http://www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-dicti=
onary" target=3D"_blank">http://www.w3.org/TR/WebCryptoAPI/#EcKeyGenParams-=
dictionary</a><br>
<br></div><div>We see:<br><br>enum NamedCurve {<br>=A0 // NIST recommended =
curve P-256, also known as secp256r1.<br>=A0 &quot;P-256&quot;,<br>=A0 // N=
IST recommended curve P-384, also known as secp384r1.<br>=A0 &quot;P-384&qu=
ot;,<br>

=A0 // NIST recommended curve P-521, also known as secp521r1.<br>=A0 &quot;=
P-521&quot;<br>};<br><br></div><div>I wonder if we might be able to get bit=
coin&#39;s curve in there<br><br></div><div>For more background on Koblitz =
curve used by bitcoin see:<br>

<br><a href=3D"https://bitcointalk.org/?topic=3D2699.0" target=3D"_blank">h=
ttps://bitcointalk.org/?topic=3D2699.0</a><br></div></div></blockquote><div=
><br></div><div>Hi All<br><br>I enuired about this and got the following re=
ply, from the chair of the crypto group:<br>
<br>[[<br>Just email <a href=3D"mailto:public-webcrypto-comments@w3.org" ta=
rget=3D"_blank">public-webcrypto-comments@w3.org</a>. It&#39;s a public lis=
t. Do definitely mention your use-cases!<br><br>I
 think there&#39;s issues of whether NSS etc. already support it. I think=
=20
the answer here is &quot;no&quot; but David can clarify. The goal is not to=
 get=20
browser vendors to write new crypto code, but to expose the crypto code=20
that already exists. <br>
<br>We still have an open issue about whether &quot;experimental&quot; regi=
stry=20
for identifiers for say, new curves that aren&#39;t in the core spec, will=
=20
be maintained. So, maybe if browsers don&#39;t support it today, it&#39;s a=
lways
 possible they might want to support it tomorrow given Bitcoin&#39;s growth=
.<br>]]<br><br></div><div>Please let me know if anyone has a use case for e=
cdsa in the browser let me know.<br><br></div><div>Or if anyone would like =
to write to the public list that&#39;s fine<br>
<br></div><div>Otherwise I&#39;ll just fire off a mail and see what they co=
me back with ...<br> </div></div><br></div></div>

--001a11c268a64b83f904ddda525f--