Updates of general interest to TATF members.

• Drummond Reed talked about the Web5 announcement from Block at Consensus 2022.
  • Block's proposal is based on the Decentralized Web Node (DWN) protocol at DIF.
• Identiverse and MyData are both happening next week.
• Vikas Malhotra shared that the IEEE group on Cybersecurity for Next Generation Connectivity Systems now has about 45 members. This group will also be exploring the use of DIDs and decentralized identity.
• Daniel Bachenheimer shared that Identity Week is the week after next in London. Dan will be a panelist on an OIX panel where they will discuss the recent announcement with ToIP. 
• Scott Perry asked about speakers for the Hyperledger Global Forum in Sept. Judith Fleenor said that she would check with Daniella.
• Judith Fleenor wanted to remind everyone of the three more guest speakers at ToIP events today. 

• ACTION: Neil Thomson to proceed with initial population of the TSWG terms wiki with assistance from Drummond Reed. 
  • Terms wiki update. - Work scheduled on the terms wiki next week. Will put existing Google Doc version link in the chat for now.
• ACTION: Tim Bouma and Drummond Reed to prepare a proposed name and scope for this "policymaker" deliverable (thomsona's suggestion is "ToIP Technology Introduction for Policymakers") and document this in a wiki page for next week's meeting.
• ACTION: Drummond Reed to add the policymaker document and the ToIP Interoperability Test Cases deliverables to the Technology Architecture Task Force wiki page.
• ACTION: All members of the Technology Architecture TF to add their proposed use cases to the Google doc as soon as possible.
• ACTION: Drummond Reed to see if Kaliya would like to present in an upcoming meeting about her perspective that the ToIP stack is very "Hyperledger Aries architecture focused" and thus not friendly to other "stacks".
  • ACTION: Drummond Reed to schedule Kaliya Young to speak to this topic for our June 30th meeting.
• ACTION: Wenjing Chu to start creating the first issues in the new GitHub repo for the ToIP Technology Architecture Specification and then post a message to Slack once he has posted them.
• ACTION: Once Wenjing is done, Drummond Reed to send a message to the Technology Stack WG mailing list announcing the start of issues management for the ToIP Technology Architecture Specification on GitHub.

Discussion of progress and issues on the working draft of the ToIP Technical Architecture Spec.

• Wenjing has posted the first issues on GitHub. 
• He started by showing the GitHub setup. 
• Currently the spec is a single Markdown file, readme.md.
• The introduction section and section titles have been provided for the whole document.
• The first issue is one of formatting and rendering issue with the ToIP stack diagram (it does not render properly right now in the published HTML version).
• ACTION: Kevin Griffin to assist Wenjing Chu check into the issue with the TechArch repo not rendering the ToIP stack graphic
• The second issue is the actual content of the ToIP stack diagram will likely need to be updated. That can wait until we are nearing completion of the spec.
• The next step is to move over other issues that are currently being discussed in the Google doc.

New issue discussion #1: Naming of components (see screenshot #1 below)

• End Systems or Endpoints?
  • These are the systems communicating via the End-to-End Principle.
• Intermediary Systems — Intermediary Node?
  • These are systems assisting in communications between the Endpoints
• Supporting System?

ACTION: Neil Thomson to add text to the Motivations and Use Cases section to explicitly talk about what is out-of-scope.

• Neil suggested that we need to talk about intermediary systems on a per-layer basis.
  • Wenjing agreed and showed that each of these systems (endpoint vs. intermediary vs. supporting) has its own stack.
  • Neil points out that there are still trust concerns with intermediary systems, such as metadata. Wenjing agreed.

ACTION: Wenjing Chu to add a new GitHub issue to propose the terms agreed to on this call: "Endpoint System", "Intermediary System", and "Supporting System".

New issue discussion #2: Resolve the question about the need for intermediary systems.

• Wenjing feels this can be resolved by reference between two proposed L2 protocols
  • DIDComm uses the terms "mediators" and "relays": https://didcomm.org/book/v2/routing
  • DWN uses "node" for intermediary systems (Web5 node): https://identity.foundation/decentralized-web-node/spec/

ACTION: Wenjing Chu to add a new GitHub issue to propose the rational for why the spec needs Intermediary Systems by including references to DIDCOMM V2 - https://didcomm.org/book/v2/routing and Web5 node - https://identity.foundation/decentralized-web-node/spec/