SUPER/META PROPOSAL: Authentication of unique DID Method names: allowing for multiple approaches

[mwherman2000]

@msporny proposed restricted approach here: #595

In this Super/Meta Proposal, I want to suggest that the DID method registration section in the spec be modified to support more than one Authentication of unique DID Method names approach that covers the following objectives:

1. Removes the burden from the reviewers
2. Removes the W3C from having to arbitrate DID method uniqueness issues
3. Produces a tangible result in terms of authenticating the uniqueness of new DID Method registration applications

The idea is to support, in the specification, more than one trivially easy-to-access Authentication of unique DID Method names approach - with the goal of giving registrants/controllers at least a couple choices that they can choose from based on time, effort, and cost. For example, tradmarking is costly especially for registrants who do not have in-house legal council - more cost effective solution(s) are also needed. The wording of the specification cannot be prejudiced for or against any registrant. In addition, a DID Method name may not be trademarkable: #595 (comment)

So what's on the table in terms of approaches (in order of strength: effectiveness, cost, time, and effort):

1. DNS Registration: Leveraging what is already available using Internet Doman Name System (DNS) domain name registration. Examples of such an approach can be found in SPEC/PROCESS PROPOSAL: To secure a unique method name, require the registration of the corresponding Internet DNS name: did-<method>. directory  #590
2. Registered trademarks per the concepts outlined here: Clarify the registration process wrt. trademarks and copyrights #595
3. Unregistered trademarks
4. No authentication of uniqueness supplied in the application

NOTE: The implication of point 4 is that we add a field to the DID Method Name registration file to specify the registrant's Authentication of unique DID Method names approach/evidence. This can be a simple text field with a link to the domain registration, a trademark statement, etc. An empty or missing field would default to class 4: No authentication of uniqueness provided. This field can also be used to ajudicate new applications that have or claim to have a stronger authentication.

Q: any additional Authentication of unique DID Method names approaches that would be simple in terms of effort, time and cost for the registrant and as well the reviewers and the W3C?

Other thoughts?

[mwherman2000]

attestation is one suggestion for the name of this new field in a DID Method registration JSON document.