Difference between revisions of "High Assurance Identifiers"

From MgmtWiki
Jump to: navigation, search
(Full Title or Meme=)
Line 1: Line 1:
 
==Full Title or Meme==
 
==Full Title or Meme==
 +
Before an [[Identifier]] can be used for High Assurance Authentication.
 +
===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
  
 
==Context==
 
==Context==
 
* [https://www.ietf.org/archive/id/draft-carter-high-assurance-dids-with-dns-05.html#RFC6698 High Assurance DIDs with DNS]
 
* [https://www.ietf.org/archive/id/draft-carter-high-assurance-dids-with-dns-05.html#RFC6698 High Assurance DIDs with DNS]
 +
* [https://ciralabs.github.io/high-assurance-dids-with-dns/draft-carter-high-assurance-dids-with-dns.html# High Assurance DIDs with DNS - on GitHub]
  
 
==Problems==  
 
==Problems==  

Revision as of 15:15, 20 September 2024

Full Title or Meme

Before an Identifier can be used for High Assurance Authentication.

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

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
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