Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <melvincarvalho@gmail.com>) id 1UZeyx-0002d4-Ix
	for bitcoin-development@lists.sourceforge.net;
	Tue, 07 May 2013 10:18:51 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.49 as permitted sender)
	client-ip=209.85.215.49; envelope-from=melvincarvalho@gmail.com;
	helo=mail-la0-f49.google.com; 
Received: from mail-la0-f49.google.com ([209.85.215.49])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UZeyw-0004vp-I3
	for bitcoin-development@lists.sourceforge.net;
	Tue, 07 May 2013 10:18:51 +0000
Received: by mail-la0-f49.google.com with SMTP id eh20so370579lab.22
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 07 May 2013 03:18:43 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.4.163 with SMTP id l3mr637328lal.34.1367921923786; Tue,
	07 May 2013 03:18:43 -0700 (PDT)
Received: by 10.112.143.38 with HTTP; Tue, 7 May 2013 03:18:43 -0700 (PDT)
Date: Tue, 7 May 2013 12:18:43 +0200
Message-ID: <CAKaEYhLH+5E0cpF1NN4VOG0Rpg7AE6aUGPG++8RO6TupndL4Dg@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e013d100c590c3304dc1e2484
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(melvincarvalho[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UZeyw-0004vp-I3
Subject: [Bitcoin-development] WebCryto standard to support secp256r1 but
	not secp256k1
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 10:18:51 -0000

--089e013d100c590c3304dc1e2484
Content-Type: text/plain; charset=ISO-8859-1

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

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

<div dir=3D"ltr">Looking at the proposed native crypto browser support (sho=
uld arrive in the next year)<br><div><br><a href=3D"http://www.w3.org/TR/We=
bCryptoAPI/#EcKeyGenParams-dictionary">http://www.w3.org/TR/WebCryptoAPI/#E=
cKeyGenParams-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">https://bitcointalk=
.org/?topic=3D2699.0</a><br></div></div>

--089e013d100c590c3304dc1e2484--