Difference between revisions of "High Assurance Identifiers"

From MgmtWiki
Jump to: navigation, search
(High Assurance DIDs with DNS)
 
(One intermediate revision by the same user not shown)
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
+
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==
Line 9: Line 10:
  
 
==Problems==  
 
==Problems==  
i saw a post on the High assurance IETF doc and i had some questions.  I don't think this is ready for public review - but i didn't see any way to comment.  Here are some questions.
+
# [[TLSA]] - with or without  Updates by: 7218, 7671, 8749
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
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
 
anyway - i lost the link and not sure how to create a real comment - its late at night so i'm lucky to get out this much.
 
  
 
==References==
 
==References==

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

Context

Problems

  1. TLSA - with or without Updates by: 7218, 7671, 8749
  2. 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