13M/ DID:DNS. Current version and ideas for improvements. Tomislav + Markus

Session 13M

did:dns - Current version and ideas for improvements

Session Convener: Markus Sabadello, Tomislav Markovski

Notes-taker(s): Ankur Banerjee

Tags / links to resources / technology discussed, related to this session:

did:dns specification - this is the main documentation on this project.

Universal Resolver (check out the did:web examples)

Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:

1. Existing DID methods
   1. Ledger-based, e.g., Indy, ION, cheqd
   2. Ledgerless ones like did:key
   3. Many people now just use did:web instead where the file is published at .well-known/did.json e.g., did:web:iiw-demo.herokuapp.com
2. Current version of did:dns
   1. Eliminates the need to have a web server, just a DNS record needed. On the flip side, it requires access to domain control.
   2. Uses record type URI, which is not very common.
   3. Current examples use did:key, which can be specified in a compressed form and expanded to a default DIDDoc.
   4. Another idea is using TXT records. Different providers have different limits
3. Future ideas
   1. Look at what ENS is doing since they are using DNS-like resolution. Other examples are Unstoppable Domains and Porkbun.
   2. Use SRV records for service endpoints? This is currently used for SIP, XMPP etc other types of services so the usage is well understood. SRV records also have