Meeting Date & Time

21 Apr 2022
- 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 Links / Recordings

NA/EU Meeting: https://zoom.us/j/99376159509?pwd=UlNyZWFNbDBnanFPeVBablNzdXpBZz09
APAC Meeting: https://zoom.us/j/99851532700?pwd=b0dvM0QxdXlCUHBwd21najlNSUN6UT09
(This links will be replaced with links to the recordings of the meetings as soon as they are available)

Attendees

NA/EU

APAC

Main Goals of this Meeting

1) Review Working Draft 01 of the ToIP Technology Architecture Specification now that it is close to content-complete, 2) review Wenjing Chu's proposal for the Reference Architecture section, 3) Discuss final preparations for a session on the spec at Internet Identity Workshop #34 next week.

Agenda Items and Notes (including all relevant links)

Time	Agenda Item	Lead	Notes
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 min	Announcements	All	Updates of general interest to TATF members. Scott Perry announced the Governance Stack WG meeting later today — 11AM PT — will be addressing layer-specific task force. Drummond Reed on eIDAS 2.0 ________ isaac henderson shared that the eSSIF-Lab TRAIN project had a successful pilot and they have some interest from the GAIN community in the trust registry and framework. GAIN (Global Assured Identity Network).
5 min	Review of previous action items	Chairs	ACTION: Wenjing Chu to: a) draft the content for section 5: Reference Architecture, and b) edit/revise/shorten the content in section 7: Architectural Layering of the ToIP Stack. ACTION: Drummond Reed to a) add initial content to sections 7.4 through 7.7, and b) convert the rest of the content from the storyline slide deck into sections 9, 10, and 11.
10 mins	Overview of updates to Working Draft 01	Drummond Reed	Per the second action item above, in the ToIP Technology Architecture Specification Google doc, Drummond has completed content for section 7 and finished moving content from the storyline slide deck into sections 8, 9, 10, and 11. Note the complete list of requirements in sections 8 thru 11. Please review carefully.
5 mins	Merging sections 3 & 4?	Wenjing Chu	Wenjing suggested we consider merging section 3: Motivations and section 4: Canonical Uses Cases & Scope Limitations. We did not have time to discuss this in the NA/EU meeting. In the APAC meeting we had consensus on the following action: ACTION: Drummond Reed to merge sections 3: Motivations and section 4: Canonical Uses Cases & Scope Limitations.
20 mins	Proposal for section 6 content	Wenjing Chu	Wenjing presented a proposal for the Reference Architecture section. See screenshots #1 through ___ below. For the full narration of his slide deck from Wenjing, listen to the recording of the APAC meeting (because Wenjing covered his entire slide deck in that meeting vs. only part of it in the NA/EU meeting).
5 mins	Final preparations for Internet Identity Workshop	Drummond Reed	We will discuss the proposed format for a session on the spec at IIW.
5 mins	Review decisions/action items Planning for next meeting	Chairs	NOTE: NO MEETING NEXT WEEK due to Internet Identity Workshop #34

Screenshots/Diagrams (numbered for reference in notes above)

#1

#2

#3

#4

#5

#6

#7

#8

Note that the dotted arrows represent different protocols but not the actual flow of messages — that is represented by the solid arrows.

The "verifiability" in slide #8 refers to secure attribution to the source. This is the core problem we are solving in a universal way.

#9

There was discussion about the separation of the "tight binding" described in this diagram. Troy Ronda shared the observation that the tight binding shown in this diagram from Wenjing Chu does not reflect how the Aries Framework Go implementation works, because it does not make the same tight binding.

Wenjing welcomed other examples.

#10