Updates of general interest to TATF members.

<From participants>

• 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

Jo Spencer 

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.

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)

Note: Drummond Reed is on vacation until August 8th.

Wenjing is out 05-18AUG2002 - totally off grid

Darrell is out 09-18AUG2022