Difference between revisions of "High Assurance Identifiers"

From MgmtWiki
Jump to: navigation, search
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==  
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==

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

  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