W3C home > Mailing lists > Public > public-credentials@w3.org > June 2017

creator prefix scheme in Koblitz signature specification

From: Kim Hamilton Duffy <kim@learningmachine.com>
Date: Fri, 02 Jun 2017 18:45:38 +0000
Message-ID: <CAB=TY87Ow9icFe9a=vvH412E-UYMUNv-ku6EnMrSt9dLpN9v1A@mail.gmail.com>
To: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
Cc: Nate Otto <nate@ottonomy.net>, Manu Sporny <msporny@digitalbazaar.com>
(Moving a side discussion to the Credentials public group)

I have 2 questions related to the creator prefix scheme mentioned in the
Koblitz signature specification

1. In the Koblitz signature specification (
https://w3c-dvcg.github.io/lds-koblitz2016/), creator is formatted as
follows:

"creator": "ecdsa-koblitz-pubkey:..."

Is the ecdsa-koblitz-pubkey: prefix a standard or generalized scheme, for
use across other curves? (I.e. other than ECDSA Koblitz?) I haven't found
any results in my searches yet. Almost all the search results are from the
blockcerts site. :)

Nate and I are interested in learning more about this w.r.t introducing it
at the Open Badges level via blockchain extensions.

2.  The sec:Key class allows only PEM-encoded public keys, as far as I can
tell. Do we envision this class being extended to handle public keys
formatted with this "ecdsa-koblitz..." prefix? I realize the context is
different (i.e. signature.creator vs publicKey), but I am interested in how
the two might be reconciled.

I opened an issue with this question in the repo where sec:Key is currently
described:
https://github.com/web-payments/web-payments.org/issues/42

Thanks,
Kim
-- 
Kim Hamilton Duffy
Principal Engineer | Learning Machine + MIT Media Lab
400 Main Street Building E19-732, Cambridge, MA 02139
12001 N. Central Expy, Suite 1025, Dallas, TX 75243

kim@learningmachine.com | kimhd@mit.edu
425-652-0150 | LearningMachine.com
Received on Friday, 2 June 2017 18:46:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 July 2018 21:19:38 UTC