Summary

• Next steps on the <network> element of the DID
  • Third (or more) level names
  • How to find the nodes of the ledger given a DID with a <network>
  • Ramifications of finding previous versions of a DID by version-id or version-time

Recording from the call: <To Be Added>

Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

Welcome and Introductions

Announcements

• TBD

Collaboration Channels

• Current hackmd document 
• indy-did-method on RocketChat - https://chat.hyperledger.org/channel/indy-did-method
• indy-did-method repo
  • ReSpec vs. SpecUp

Previous Discussion:

• The <network> element of the DID – did:indy:<network>:<id> will be an arbitrary string (see meeting notes from last meeting).

  Approach	Discoverability	Decentralized Naming	(Limited) Verifiability	Human Friendly	Conciseness	Dependencies
  Hash of Domain Genesis File	No	Yes	Yes	No	Yes	Registry or Config
  Domain Name	Yes	Yes	No	Yes	No	DNS
  Arbitrary Name	No	No (collision risk)	No	Yes	Maybe	Registry or Config
  Hash and Domain Name Alias, as in TrustBloc	Yes and No	Yes	Yes	Yes and No	Yes and No	DNS and Config
  Arbitrary Name + Hash	No	Yes	Yes	Yes	No	Registry or Config

• The in-call discussion about the proposals:

  • Eliminated the DNS-based one as not desirable because of dependency on DNS
  • Eliminated the hash and DNS-based alias because of the complexity in using the two names for the identifier in signing scenarios, and the use of DNS.
  • Eliminated the hash only approach because of the lack of benefit of doing the hash vs. the downsides
    • The verifiability in using the hash is lost by using just 5 characters, but using a sufficient number makes the identifier too long
      • Micha generated a new Sovrin genesis file with a matching hash by varying only the alias name of one of the nodes in 30 minutes
      • Since we assume there will be in the low thousands of networks at the outside, the decentralization inherent in using the hash is not crucial
  • Eliminated the hash + arbitrary name because the hash is not providing additional value.
  • Leaving "Arbitrary Name" as the selected solution.

Discussion:

• Third level names for subsidiary ledgers – e.g. Sovrin Staging and Sovrin Builder net?
  • We could use ":", but that creates lots of colons.
  • Andrew Whitehead mentioned in chat that "." is a valid character. What about that?
• How to find the nodes of the network once the ledger is known?  Config files, registries, gossiped names, etc.
• How to find previous versions of DIDs and what are the implementation ramifications of that?
  • <did>?version-id=<txnid>
  • <did>?version-time=<timestamp>