W3C home > Mailing lists > Public > public-credentials@w3.org > September 2021

RE: Mozilla Formally Objects to DID Core

From: Jim St.Clair <jim.stclair@lumedic.io>
Date: Thu, 2 Sep 2021 15:22:53 +0000
To: Tom Jones <thomasclinganjones@gmail.com>, Markus Sabadello <markus@danubetech.com>
CC: Credentials Community Group <public-credentials@w3.org>
Message-ID: <MW4PR04MB715606B476B5105F5B68E97C9FCE9@MW4PR04MB7156.namprd04.prod.outlook.com>
“Flexibility on security is not a feature that I would brag about.”


The opposite of flexibility is rigidity, which historically makes security “brittle”, so I’m not sure I understand…

Best regards,
Jim St.Clair
Chief Trust Officer
jim.stclair@lumedic.io<mailto:jim.stclair@lumedic.io> | 228-273-4893
Let’s meet to discuss patient identity exchange: https://calendly.com/jim-stclair-1

From: Tom Jones <thomasclinganjones@gmail.com>
Sent: Thursday, September 2, 2021 10:19 AM
To: Markus Sabadello <markus@danubetech.com>
Cc: Credentials Community Group <public-credentials@w3.org>
Subject: Re: Mozilla Formally Objects to DID Core

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Flexibility on security is not a feature that I would brag about.


On Thu, Sep 2, 2021 at 12:34 AM Markus Sabadello <markus@danubetech.com<mailto:markus@danubetech.com>> wrote:

I sympathize with Mozilla's comments about centralized methods and proof-of-work methods, and I believe these concerns could be addressed in the DID Rubric and DID Implementation Guide documents, without necessarily requiring changes to DID Core itself.

Mozilla's other comment about lack of interoperability is however hard to unterstand for me.

The whole point of DID methods is to ENABLE interoperability between heterogeneous identifier systems.

Some use cases will only use a single DID method and not be interoperable with others.
Some DID methods will become very popular and be widely interoperable across many different systems.
Some DID methods may become standardized (e.g. did:key, did:web) and therefore "effectively mandatory".
Some use cases will want to support as many DID methods as possible, even less popular ones.

This flexibility is a feature, not a bug.

On 02.09.21 04:11, Orie Steele wrote:

The objection mentions comments from Google and Microsoft, but does not link directly to them.

Does anyone have a direct link to the comments from Google and Microsoft?


Chief Technical Officer


(image/png attachment: image001.png)

Received on Thursday, 2 September 2021 15:23:09 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:25:22 UTC