PROPOSAL: To secure a unique method name, require the registration of the corresponding Internet DNS name: did-<method>. directory

[mwherman2000]

For example,

• did:ns -> http://did-ns.directory
• did: object -> http://did-object.directory

There would be no requirement to implement or use the registered domain. It would be like buying an automobile license plate and never placing it on a vehicle (which is OK).

Second, this would remove the W3C from the conflicting method name problem.

Third, existing W3C registrations would be "grandfathered in"; i.e. not required to have the DNS name registration but it would still be recommended.

Other thoughts?

[brianorwhatever]

This mechanism is highly vulnerable to trolling.

It also puts an ongoing financial burden on DID method registration/maintenance.

[mwherman2000]

It also puts an ongoing financial burden on DID method registration/maintenance.

So does trademarking. Checkout #597 for a hybrid approach.

[andrewwhitehead]

I don't believe it's appropriate to require this as it could be seen as a handout to Identity Digital, the registrar for .directory. There would also be a gold rush for squatting on existing DID methods.

[mwherman2000]

Hi @andrewwhitehead, your feedback is a valid consideration.

Please checkout the Super/Meta Proposal that proposes the inclusion in the spec of multiple authentication of unique DID Method names approaches (in addition to the one described here) and the one @manu described elsewhere.