Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added links

...

Main Goal of this Meeting

Start planning for developing and publishing the ToIP the ToIP Technology Architecture Specification Architecture Specification as a Core Four deliverable.

...

TimeAgenda ItemLeadNotes
5 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
  • 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
15 minsTask Force ReportsTF Leads

Trust Registry TF — Darrell O'Donnell

  • --

ACDC TF — 

ACDC TF — Drummond Reed

 
  • -- and Kevin Griffin gave several presentations on ACDC at Internet Identity Workshop.
  • Attendees recognized that ACDC is a "fourth credential flavor" in addition to the three flavors supported in the W3C Verifiable Credentials Data Model 1.0 specification (the ISO mDL spec is a fifth).

Design Principles TF — Drummond Reed

  • Progress was somewhat delayed by Internet Identity Workshop last week, but the first draft of the Design Principles for the ToIP Stack should be completed this week.
  • Work is starting on revised graphics throughout—see the agenda items below.
  • Antti Kettunen has made a comment on the second principle and will write it up. He is excited about building the "API of Me".

Technology Architecture TF — Drummond Reed

  • This TF is now going to start moving full speed — see agenda item below.
1 minApprove Design Principles for the ToIP Stack as Draft DeliverableChairs

Call for consensus:

15 minsInternet Identity Workshop Tech HighlightsAll IIW Attendees
  • Premature Standardization & Premature Interoperability (Darrell)
    • We still have a long ways to go forward on standards.
    • We have not done anything dead wrong, but we don't have real interoperability yet.
--
    • Six or seven governments are operating Hyperledger Indy and Hyperledger Aries code bases but are not yet actually fully portable.
    • Steve McCown pointed out that we have a limited set of companies and developers building out ToIP and they seem to be compartmentalized by platform.
    • Darrell agreed with Steve, but pointed out the Aries Interop Test Suite. He hopes that it will enable the different platform implementations to actually interop.
    • Darrell shared a story about the interop challenges in the geospatial mapping standards arena. All of the web mapping servers achieved interop at a specific version of the spec that proved to be sufficient for the market needs.
    • Steve agreed that the different platform implementations are all similar. His company has been using a Mozilla toolkit called Uniffi that can lets you use the same toolkit in multiple places. It provides something more stable across the multiple toolkits — it is the easiest way to take a common library and implement it everywhere.
    • Darrell would like Steve to share that with the Aries Interop effort.
    • Antti observed that the EU Digital Identity Wallet initiative is amplifying efforts around feature comparisons vs. ISO mDL standards. If we look too far down the road, we're going to lose the battle to ISO mDL.
  • mDL sessions — Drummond Reed reported that there were several sessions on mDL moderated by Andrew Hughes, who is now Director of Standards at Ping Identity.
    • the mDL family of specs (not all of which are finalized yet) will tackle everything needed to establish real market interop, including the protocols.
    • There was consensus that this was the level of interop that the Aries stack needs to reach — and the ToIP stack as quickly as we can define a V1.
  • DIDComm — Drummond Reed
  • BBS+ with LD Signatures — Drummond Reed
    • Drummond did not attend this session but reported that Brent Zundel did and he said that the two Japanese cryptographers that gave this session showed a very compelling demonstration of how they solved the privacy leakage problems in the MATTR implementation.
10 minsRevised ToIP stack graphicDrummond Reed
  • We are producing a new version of the static ToIP stack diagram to use with our Core Four deliverables.We will review the proposed changes .
  • We reviewed the proposed changes in this Google doc.
  • They generated a lot of discussion, starting with "Agent / Wallet Governance Frameworks" at Layer 2.
  • We ran out of time so we agreed to the following action item:
  • ACTION: ALL TSWG members to review and comment on the proposed changes to the static ToIP stack diagram in this Google doc.
10 minsToIP Technology Architecture SpecificationDrummond Reed
  • This is the final deliverable in the Core Four.
  • One key task we can begin working on now is a technical diagram of the ToIP Technology Stack as a protocol stack—we need this for the Design Principles for the ToIP Stack paper.
  • Should we begin having weekly meetings of this TF in order to finish this deliverable in November? The answer was yes.
  • ACTION: Darrell O'Donnell and Drummond Reed to schedule a weekly ToIP Technology Stack TF meeting in the 7AM PT / 10AM ET time slot.
  • Should we establish a ToIP Architects Council consisting of ToIP members who are recognized architects for decentralized digital trust infrastructure who we want closely reviewing this specification?
  • We will take up this question in the new ToIP Technology Stack TF meeting.
5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

Screenshots/Diagrams

...

Image Added

Decisions

  •  Sample Decision Item

Action Items

  •  Sample Action Item

Action Items