Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Meeting Date & Time

  •  
    • NA/EU 07:00-8:00 PT / 14:00-15:00 UTC 
    • APAC 1:00-2:00PM PT / 20:00-21:00 UTC

Zoom Meeting

...

Recordings

Main Goal of this Meeting

TODOReview progress on the ToIP Technology Architecture Specification draft.

Agenda Items and Notes (including all relevant links)

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:
5 minAnnouncementsAll

Vikas Malhotra IEEE CyberSecurity group (SSI/ToiP related) Link

Daniel Bachenheimer - will get an update on working groups for SSI Digital ID at ISO

Tim Bouma Digital Identity Lab of Canada update: Hyperledger URSA Code Review. In conversations with groups outside of ToIP, looking for a super simple ToIP (Architecture) four-layer (stack) model for external groups. Observation that : Layers 1 and 2 are primarily technical and Layers 3 and 4 are management. The document needs to provide an overview (and pointers to more detailed docs) as to how to achieve technical capability.  

EIC2022 - Feedback from Drummon Reid Drummond Reed, Judith Fleenor other attendees was that ToIP-related discussions were well recievedreceived

5 minReview of previous action itemsChairsNone.
30 minsSpecial topic #1Walkthrough of progress with the Tech Arch Spec (draft)

Review of diagrams, organization and content for the ToIP Tech Arch Spec - Working Draft, with a walk-through from Wenjing Chu 
Wenjing Chu The main update for today is sections 5.1 and 5.2 (plus embedding the diagrams from the IIW presentation). 
The introduction Tech Stack illustration needs to be simplified, which should be done once the spec core ideas have been resolved.

5.1 outlines the goals and design principles for the architecture. Each of the bullet points (and this is a general comment for all lists in the document) will need to be expanded both in this (top-level) spec and in more detailed documents. For example: what, precisely (in both human and technical terms), do Verifiability, Confidentiality and Privacy mean?

The focus of the ToIP stack are is layers 1, 2 & 3, which lay the foundation on which Layer 4 is built. Layer 4 will only be discussed in broad terms

Additional comments are in the Tech Spec itself

The discussion ended at the end of 5.2.2 (call end).

<To be continued in the afternoon session and following week>

10 minsSpecial topic #2Documentation Management (of the Tech Arch Spec and similar related documents:)

As the Tech Arch Spec is getting filled out, it's quickly becoming clear that Google Docs and Google Docs comments need to (longer-term) move to a GitHub type solution, using issues vs comments (particularly detailed, verbose or visual/diagram comments).

Discussed today was which way to go - what the ACDC ToIP team is using, or GleifGLEIF, etc. and whether the doc format is pure MD or something that will eventually conform to the IETF publishing format. Judith Fleenor was on the call and needs to be part of selecting a solution.

10 minsSpecial topic #3Discussion on Tech Arch Spec sections 5.1, 5.3, 5.6, key term definitions 

The Afternoon/APAC call was an in-depth discussion on sections 5.1, 5.3 and 5.6 of the Tech Arch Spec. Participants included @SamSmith @Wenjing Chu @Judith Fleenor @Neil Thomson. The minutes (from transcribing the recording) have been re-arranged into topics and sub-topics in what was a free-ranging discussion. As this is a long discussion, HackMD (Markdown) has been used to make it easier to re-use this material as the Tech Arch Spec authors see fit.

https://hackmd.io/cRNAX1ImRGOucds_ntXI2Q

5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

ACTION: Wenjing Chu Will continue to fill in sections of the document in section order. The weekly schedule going forward will be reviewing both new work and comments as sections are completed.

Screenshots/Diagrams (numbered for reference in notes above)

  1. Tim Bouma alternative simplified view of Tech Arch top-level cloud diagram:


Decisions

  • Sample Decision ItemNone

Action Items

  •  Sample Action Item
  •  ACTION: Wenjing Chu Will continue to fill in sections of the document in section order. The weekly schedule going forward will be reviewing both new work and comments as sections are completed.