-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Register dnsValidationDomain
property
#566
Conversation
I think this is definitely useful, and the spec already looks very advanced..! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sync names. PR title should be updated too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once @davidlehn's changes are incorporated. You might want to rebase this branch before we merge it, @jessecarter111
dnsDomain
propertydnsValidationDomain
property
Agree on example change. Co-authored-by: Manu Sporny <[email protected]>
4307e8f
to
7c4d18e
Compare
Pinging for visibility on the workflow approval. Branch was rebased off main fork and requested changes added. |
The "dnsDomain" property, as outlined in the High Assurance DIDs with DNS, helps to establishes a clear and verifiable link between a non web based DID and a DNS domain. This linkage leverages the existing trust infrastructure of the DNS, which is widely recognized and relied upon. By incorporating the "dnsDomain" property, non web based DIDs can benefit from the established trust model of DNS, providing an additional layer of assurance for entities interacting with the DID. It also enables the ability to associate a non web based DID with a DNS based identifier in accordance to the spec, without infringing upon the usage of the "alsoKnownAs" property or "linkedDomains" service type.
Preview | Diff