- From: Mark Watson <watsonm@netflix.com>
- Date: Fri, 7 Mar 2014 16:08:19 -0800
- To: Lu HongQian Karen <karen.lu@gemalto.com>
- Cc: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
- Message-ID: <CAEnTvdAVm+h2iunVyvFi+eA=czvVDDHXrYqi4AcNZJeMh6_rvA@mail.gmail.com>
Thanks Karen. +1 to referencing the free versions. ...Mark On Fri, Mar 7, 2014 at 4:02 PM, Lu HongQian Karen <karen.lu@gemalto.com>wrote: > Mark, > > > > May be we should reference the latest standards from NIST, which are free > to download? > > > > Here are the relevant NIST documents and information: > > > > NIST.FIPS 186-4 (digital signature standard, July 2013) specifies ECDSA. > The ECC key pair generation is in the appendix B. > > > > NIST.SP 800-56A v2 (recommendation for pair-wise key establishment schemes > using discrete logarithm cryptography, May 2013) describes ECDH. Section > 5.6.1.2 says: "For the ECC schemes, each static and ephemeral private key d > and public key Q shall be generated using an approved method (see Appendix > B of [FIPS 186])..." > > > > So the key pairs for ECDSA and ECDH are (or can be) generated the same > way, at least from the NIST perspective. > > > > Regards, > > Karen > > > > > > *From:* Mark Watson [mailto:watsonm@netflix.com] > *Sent:* Tuesday, March 04, 2014 7:46 PM > *To:* public-webcrypto@w3.org > *Subject:* Elliptic Curve key definitions in X9.62 and X9.63 > > > > I'm hoping that someone on this list can answer the following question to > save me from buying and wading through these two ANSI documents. > > > > Is the definition of an Elliptic Curve Key Pair in X9.62 (which we > reference for ECDSA) and X9.63 (which we reference for ECDH) the same ? > > > > It would seem that it must be, but without the documents in front of me I > can't be sure. > > > > ...Mark > > ------------------------------ > 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 Saturday, 8 March 2014 00:08:52 UTC