Page History

• Start recording
• Welcome & antitrust notice
• Introduction of new members
• Agenda review

• Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
• New Members: none

IIW

• Likely revisit again next week when our US brethren
• DIF / ToIP Collaboration 

Darrell: - building blocks are "there", Trust Registries are missing

Andor:

• Trust Registry - agreement
• DIDAuth missing activity.
  • Darrell: while DIDAuth has been around for years, there is no consistency in what it means and how it applies. This results in lack of progress. 
• Building Blocks for adoption
  • two big blockers (which are?? NJT)
  • DIDAuth - e.g. how do I prove I own a DID... as a major problem
• Trust Registry - particularly decentralized/centralized; online/offline use.
  • Tim: "managed" vs. "unmanaged" as terms to consider.

Tim:

• Governments are leaning in - "identity" has bee been backed off; credentials becoming more important; Trust Registries getting attention
• Signing - reverse consequence (limited innovation and created vendor capture)
• Raised a concern about DIDDocs and the attack vectors. 

Antti:

• Role The role of government is to be light in some areas (e.g., where the private sector should lead) but create some guardrails to protect government and citizen interests.
• Findy (Finland?) has formal government involvement and is starting with a broad understandng understanding that the bounds aren't quite clear , but directionally align with ToIP.
  • "connectivity is its own reward." 

github

Confluence page updated for v2 work to begin:

• formal page ToIP Trust Registry Protocol Specification
• Loose capture of requirements Trust Registry Protocol v2 - Loose Capture

ACTION:

• Review decisions/action items
• Planning for next meeting