Difference between revisions of "High Assurance Identifiers"
From MgmtWiki
(→High Assurance DIDs with DNS) |
|||
| Line 2: | Line 2: | ||
Before an [[Identifier]] can be used for High Assurance Authentication it must be issued by a known issuer to a known device and wallet. | 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=== | ||
| − | + | An IETF draft RFC method for improving the authenticity, discoverability, and portability of Decentralized Identifiers (DIDs) by utilizing the current DNS infrastructure | |
| + | * [https://docs.google.com/presentation/d/1u6GK7oWw-ewB3lONncI1CfcMpiJ2zUT8LrUGRLuV1w8/edit?pli=1#slide=id.p High Assurance DIDs with DNS] slide deck from 2024-09 | ||
==Context== | ==Context== | ||
Latest revision as of 15:49, 21 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
An IETF draft RFC method for improving the authenticity, discoverability, and portability of Decentralized Identifiers (DIDs) by utilizing the current DNS infrastructure
- High Assurance DIDs with DNS slide deck from 2024-09
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
