Meeting Date

28 Oct 2021

Zoom Meeting Link / Recording

https://zoom.us/rec/share/7Dyta_-sQViOAeFRbyuJV_0uJHm70Oc39Mi7Vokd-P7zmUJGJGlXKrc9E--rImg.bpkr-J33e14F5Xu1?startTime=1635429989000

Attendees

Main Goal of this Meeting

First formal meeting of this Task Force! Establish goals, timeframe, and dive into the layer naming and architectural diagram topics.

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: This was the first meeting, so all the members listed above did brief intros.
10 min	Background on the Core Four and goals of this TF	Chairs	See the diagram of the Core Four on the Introduction to ToIP wiki page. The goal of this TF is to produce the ToIP Technology Architecture Specification as quickly as possible, but in any case to have it reach final ToIP Approved Deliverable status before the year-end holidays.
10 mins	Collaboration and editing	Chairs	Documents: This is the Google doc where we are starting to draft the specification. This is the original Hyperledger RFC defining the ToIP stack. This is the current draft of the Design Principles for the ToIP Stack recommendation. We plan to hold weekly Zoom meetings One for NA/EU — Thursdays 07:00-8:00 PT / 14:00-15:00 UTC One for APAC — tentatively Thursdays — what time works? The proposed time is 15:00-16:00 PT / 22:00-23:00 UTC ACTION: Drummond Reed to see if 15:00-16:00 PT / 23:00-24:00 UTC (after daylight savings) will work for APAC members and then set up the calendar invite starting Thursday Nov 4. We need to work async as well: In the Google doc In the #tswg-tech-arch-tf Slack channel Do we need a mailing list? Darrell O'Donnell suggests to just use the TSWG list. ACTION: Drummond Reed to work with LF staff to add TF members to the TSWG mailing list.
10 mins	Layer Naming	Drummond Reed	See this Google Slides deck (anyone may access or comment; ask for edit permission) We discussed this briefly but decided that layer naming decisions should follow the protocol stack diagram work.
20 mins	Protocol Stack Diagram	Drummond Reed	See this Google Slides deck (anyone may access or comment; ask for edit permission) Submissions so far include Drummond Reed, Jo Spencer, and Wenjing Chu Every TATF member is invited to submit their version/vision Wenjing Chu explained the logic behind his proposal for the four layers. Antti Kettunen did the same thing for the proposal he made in the deck. At that point, we ran out of time but agreed to continue the work asynchronously. ACTION: Drummond Reed to add edit permission for Scott Perry and offer it up to any other member who wants to offer their proposal. ACTION: ALL to submit any new or revised proposals to the Protocol Stack Diagram slide deck.
5 mins	Review decisions/action items Planning for next meeting	Chairs	Our next meeting will focus on the Protocol Stack Diagram work.

Screenshots/Diagrams (numbered for reference in notes above)

Decisions

DECISION: We will not use a separate mailing list for the Technical Architecture TF but instead us the Technical Stack WG mailing list.

Action Items

ACTION: Drummond Reed to see if 15:00-16:00 PT / 23:00-24:00 UTC (after daylight savings) will work for APAC members and then set up the calendar invite starting Thursday Nov 4.
ACTION: Drummond Reed to work with LF staff to add TF members to the TSWG mailing list.
ACTION: Drummond Reed to add edit permission for Scott Perry and offer it up to any other member who wants to offer their proposal.
ACTION: ALL to submit any new or revised proposals to the Protocol Stack Diagram slide deck before our meeting next week.