Page Comparison

Summary:

...

26 Apr 2023 (7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)

	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

Attendees                   

...

• IIW Recap
  • DIDComm v2 Interopathon
  • Lots of OpenID4VC sessions 
    • AFJ adding already
  • Bifold and the BC Wallet
    • Lots of Interest
  • AI
    • Trust Issues
    • 'Our' stuff has some of the solution to trust
    • Data more important than the code
    • Previously 'anonymous' data or patterns can be brought to light.
  • KERI
    • New Theme - Security, Privacy, Authenticity, and Confidentiality
  • Trust Registry Discussions
    • Not lots of resolution
  • Low ISO and W3C Topics
  • OWF Sessions
  • Red Teaming Identity - Air Force Research Lab
    • Presentation slides:  

      Widget Connector
      url https://docs.google.com/presentation/d/1fuxW7-IH2Vdohr86PGTYEvjqK-7bwcQk8Is9eDXRiWA/edit#slide=id.g232dcea63e1_2_55

       
    • Looking for vulnerabilities in libraries
    • Spec where a piece is listed as optional
      • recommend not implementing anything listed as optional
      • a number of vulnerabilities hover around optional features
  • Revocation
  • OCA
  • Government agency interest in the current state of Digital Identity
    • New Legislation, and what should be in it.
    • DHS - hold biometric and biographic repos
• LF Digital Trust Initiative
  • Potential Container for HL, ToIP, OWF, and DIF
  • Organizational Opportunities for Aries
  • Interested in conversations?
• DID Peer Update?
  • Alex added PR for Method 3: https://github.com/decentralized-identity/peer-did-method-spec/pull/49'
• DIDComm v2.1
• AIP 3 Next Steps

Not Discussed Notes from last week...

• DID Peer 2/3 – processing approach – is this the plan:
  • Identifiers:
    • Long Identifier – as defined today, entire encoded DIDDoc in identifier
    • Short identifier is the first 22(?) characters of 64 character string sha256 of long identifier (or something else?)
  • On receipt of a did:peer:3<identifier>, process as follows:
    • Detect length of identifier — short or long (assumption: long peer:did:2 will never be less than 23(?) bytes)
    • If short - resolve DID locally to get DIDDoc - on success, exit
    • If short and resolution failed — error, exit
    • If long
      • Convert long DID to short DID - resolve DID locally to get DIDDoc - on success, exit
    • If long and short DID resolution failed
      • Resolve long DID locally to get DIDDoc — on success, exit
    • if both short and long DID resolution fails
      • If on a “create DID” step (e.g. receiving DID Exchange “request” or “response” or DIDComm 2 new protocol step)
        • Extract DIDDoc from long DID, store short DID and DIDDoc, get DIDDoc — on success, exit
    • Otherwise — error

Other Business

Future Topics

...