Discover DIDs from other identifiers

[peacekeeper]

DIDs can potentially be discovered from other identifiers such as HTTP URIs, domain names, or email addresses, using e.g.:

• DNS entries in a domain name's zone file (see here for a draft spec).
• HTML code embedded in a web page (such as a Verifiable Credential stating that "Domain example.com is run bydid:example:1234.")
• WebFinger

We should discuss if and how these protocols should be specified, and what implications (if any) this has for the DID Resolution spec.

Also consider "backreferences" from a DID to those other identifiers that point to a DID.

[dmitrizagidulin]

Perhaps we can also offer a /.well-known/ based approach? Like the Apple AASA files

[TomCJones]

i would support a .well-known path - most new implementations of this require https://

[peacekeeper]

See related work at DIF: https://github.com/decentralized-identity/well-known and decentralized-identity/interoperability#7

[peacekeeper]

Also see https://datatracker.ietf.org/doc/html/draft-mayrhofer-did-dns-05 and https://www.ietf.org/archive/id/draft-carter-high-assurance-dids-with-dns-05.html

[pchampin]

This was discussed during the did meeting on 24 October 2024.

View the transcript

DID Resolution

<markus_sabadello> https://github.com/w3c/did-resolution/issues?q=is%3Aopen+is%3Aissue+label%3Adiscuss

markus_sabadello: please see above link
… there are four initial feedback issues. we need to check if there are other topics and possibly split them up.

Wip: the issues seem broad. we need people to look at them and help split them.

<markus_sabadello> w3c/did-resolution#8

markus_sabadello: issue 8 is six years old, but could be interesting to look at
… this one talks about linking DIDs to domain names, other things too.
… this could be a topic at IIW next week.
… should we add any of that language to DID resolution spec?
… or at least we make the spec flexible enough to support it.

Wip: good discussion today.
… next week is APAC meething time.

---