Difference between revisions of "High Assurance Identifiers"
From MgmtWiki
| Line 1: | Line 1: | ||
==Full Title or Meme== | ==Full Title or Meme== | ||
| − | Before an [[Identifier]] can be used for High Assurance Authentication. | + | Before an [[Identifier]] can be used for High Assurance Authentication it must be issued by a known issuer to a known device and wallet. |
===High Assurance DIDs with DNS=== | ===High Assurance DIDs with DNS=== | ||
A method for improving the authenticity, discoverability, and portability of Decentralized Identifiers (DIDs) by utilizing the current DNS infrastructure | A method for improving the authenticity, discoverability, and portability of Decentralized Identifiers (DIDs) by utilizing the current DNS infrastructure | ||
| Line 9: | Line 9: | ||
==Problems== | ==Problems== | ||
| − | + | # [[TLSA]] - with or without Updates by: 7218, 7671, 8749 | |
| − | + | # Is this 1-Identifier 2-Authentication 3-Federation, It seems to be mix - perhaps from the view of the verifier - unclear its always good to know who a std is directed at and who must comply with what | |
| − | |||
| − | |||
==References== | ==References== | ||
Revision as of 15:20, 20 September 2024
Full Title or Meme
Before an Identifier can be used for High Assurance Authentication it must be issued by a known issuer to a known device and wallet.
High Assurance DIDs with DNS
A method for improving the authenticity, discoverability, and portability of Decentralized Identifiers (DIDs) by utilizing the current DNS infrastructure
Context
Problems
- TLSA - with or without Updates by: 7218, 7671, 8749
- Is this 1-Identifier 2-Authentication 3-Federation, It seems to be mix - perhaps from the view of the verifier - unclear its always good to know who a std is directed at and who must comply with what
