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

DID Spec Closure Process: Cryptographic Key Material Proposals for the DID Specification

From: =Drummond Reed <drummond.reed@evernym.com>
Date: Tue, 19 Dec 2017 01:20:03 -0800
Message-ID: <CAAjunnaWtuf1txS5ges-iBuJOT4TtfhnF9za2JSy=2VHEAL0zg@mail.gmail.com>
To: "W3C Credentials CG (Public List)" <public-credentials@w3.org>, "W3C Digital Verification CG (Public List)" <public-digital-verification@w3.org>
Cc: Kim Hamilton Duffy <kim@learningmachine.com>
Per an action item from the last DID Spec Closure call (Thursdays at
10AM Pacific Time), I have created a new Google doc
to help us present and discuss proposals regarding one specific set of
issues. From the introduction:

Over the past month the CCG has been holding DID Spec Closure meetings. One
of the primary issues being discussed is how DID documents can best enable
identity owners to publish the public keys or other cryptographic material
they need to make available in a DID document in order to bootstrap trusted
interactions. Note that in many cases this cryptographic key material will
be used in conjunction with service endpoints that are also published in
the DID document.

The purpose of this document is to enable CCG member(s) who have a
particular point of view on how best to represent cryptographic key
material in a DID document to present their proposal in one place so that
the full group can evaluate all the proposals and ideally find an
intersection that everyone can live with.

I am happy to review this quickly on tomorrow's CCG call, but it's pretty
simple: the action item is for all CCG members who have a particular POV on
this subject to fill out the template for their proposal—and add comments
to other proposals as is helpful.

I'd really like to focus discussion on the next (and final 2017) DID Spec
Closure call this Thursday on these proposals.


Received on Tuesday, 19 December 2017 09:20:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:17 UTC