Meeting Date & Time

Aug 3, 2022 This Task Force holds TWO meetings weekly on Thursdays at the following times (to cover global time zones):
- NA/EU 07:00-8:00 PT / 14:00-15:00 UTC
- APAC 18:00-19:00 PT / 01:00-02: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 Meeting

@Darrell O'Donnell
@Daniel Bachenheimer
@Neil Thomson
@Kevin Dean
@Vikas Malhotra
@Mattia Zago
@sankarshan

APAC Meeting

@Darrell O'Donnell
@Neil Thomson
@Jo Spencer
@thomsona

Main Goals of this Meeting

1) Wrap up discussions and actions on proposed changes to section 4, action items on Core Terms and Normative Requirements
2) Review Jo Spencer's "Mental Model" for components in the ToIP stack
3) Continued review of sections 7-11

Agenda Items and Notes (including all relevant links)

Time	Agenda Item	Lead	Notes
3 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. <From participants>
2 min	Review of previous action items	Chairs	ACTION: ALL MEMBERS to continue to review sections 7 through 11 of the ToIP Technology Architecture Specification to add any final comments or suggestions. ACTION: Jo Spencer - proposal on EndPoint Systems/Intermediary Systems communication Req's (discuss on Slack) ACTION: Neil Thomson - proposed communication used by EndPoint Systems and Supporting Systems, on-node Support System inter-communication and cross-network interaction within a Support System. ACTION: @Drummond Reed to raise an GitHub on this topic [[DO: WHAT TOPIC??]] as it will require more in-depth discussion that is feasible in Google docs (and because we are now trying to move all new issues to GitHub). ACTION: @Neil Thomson update the TATF "design principles" to include "detailing" of Use cases from Tech Arch through test cases. ACTION: @Neil Thomson update the Use Case table to include column Normative Requirement(s) involved in each use case ACTION: @Darrell O'Donnell to suggest a replacement for Figure 2 (development progression) ACTION: All to review Jo's model (below) for future discussion
15 mins	Review proposed ToIP mental model	@Jo Spencer	Review proposed "Mental Model" for components in the ToIP System model - Diagrams #1 (below) Consensus - a good starting point. This can be reviewed, extended, etc. as a separate deliverable - nothing is currently dependent on this diagram.
15 mins	Review any comments on section 4 before moving to MD/Git	@Darrell O'Donnell @Wenjing Chu	See this Google Doc for proposed revisions to section 4 COMPLETE! READY for Doc→ Github Action Item → @Neil Thomson create a Project management google doc (to start) to discuss details of process across the different tracks/work to complete the tech arch spec (issues & resolution, updates) A list of related deliverables and their dependencies. This includes ToIP primer for Policy Makers Design Principles Use cases Action Item - @Neil Thomson - update use case strategy for the Tech Arch - need for in-layer, component-specific, and cross-layer use cases. The latter are critical to overall compliance testing and interoperability.
15	TAS REVIEW	@Darrell O'Donnell @Wenjing Chu	Discussion of progress on the working draft of the ToIP Technology Architecture Specification: Google Doc version - sections 6 and earlier are moved to GitHub GitHub Markdown version GitHub issues list Discussion on revamping the Layer diagram (to be continued in the APAC call - issue - The overall layer diagram includes Layer 1 having Transport, Encryption/signing services and Commitments (verifiable identifiers, etc.). Yet all the illustrative examples in Section 7 only include Transport in the diagrams. How do we change the diagram to better reflect the inter-layer and cross-layer dependencies and interactions of all types. The following is a partial proposal: Much discussion on this diagram, without resolution. Possibly split into different diagrams to illustrate Interaction Protocol stack Trust support stack Authenticity stack (cryptographic trust dependencies)
5 mins	Review decisions/action items Planning for next meeting	Chairs	Note: @Drummond Reed is on vacation until August 8th. Wenjing is out 05-18AUG2002 - totally off grid Darrell is out 09-18AUG2022

Screenshots/Diagrams (numbered for reference in notes above)

#1

Decisions

Sample Decision Item

Action Items

Sample Action Item

2022-08-03 TATF Meeting Notes