Meeting Date & Time
...
- NA/EU meeting: 08:00-09:00 PT / 16:00-17:00 UTC
- APAC meeting: 18:00-19:00 PT / 02:00-03:00 UTC
See the Calendar of ToIP Meetings for exact meeting dates, times and Zoom links.
Zoom Meeting
...
Recordings
- NA/EU Meeting: https://zoom.us/rec/share/Oy3EFP6EmzLpsWqfnL17Ff2Mw0cxaoxEkpon4NRu14NWc-u1tVnBNRQbgshFZQU.cMU7GLRGYkf_axIy
- APAC Meeting: https://zoom.us/rec/j/96772881287?pwd=bzZUNXRhVUNzVjR2Z3B2cVVxc2ZUZz09
...
Attendees
NA/EU:
...
Agenda Items and Notes (including all relevant links)
| Time | Agenda Item | Lead | Notes |
| 3 min |
| Chairs |
|
| 2 min | Review of previous action items | Chairs |
|
| 10 mins | Term for VID-to-VID directed graph edge | Drummond Reed | See this GitHub discussion and also diagram #1 below. This resulted in a long discussion on the NA/EU call, much of which was subsequently captured in posts to the GitHub discussion thread. On the APAC call, the final conclusion was reflected in diagram #2 below and in this decision, proposed by Ed Eykholt: DECISION: At least through the Implementers Draft, in the TSP spec, we will continue to use the term "relationship" or "VID relationship" when referring to the VID-to-VID graph edge (in a graph theory sense). We will continue to test that terminology to see if any adjustment or additional terms (such as those related to the concept "sessions") are needed. ACTION: Drummond Reed to draft a callout paragraph for the spec that explains why we are using the term "relationship" and not "connection" or "channel". |
| 10 mins | Diagram of TSP Routed Encrypted Message Through Intermediaries | Ed Eykholt | See this diagram (also copied as screenshot #3 below) that Ed created to help him understand the section of the Working Draft titled TSP Routed Encrypted Message Through Intermediaries. On both the NA/EU and APAC calls, we had an extensive discussion about this diagram and the "routing" concepts it represents. Everyone agreed that it helped deepen our understanding of how "routing" worked. Wenjing Chu noted that the term "routing" is almost misleading because the concept of routing in TSP is very different than it is in Internet routing. Drummond Reed suggested that this might mean we should put another callout in the spec On the APAC call, Tahoe Blue asked how routes are discovered. Wenjing Chu gave a basic explanation but Jeff was not satisfied. ACTION: Tahoe Blue to review the Working Draft to determine if his question is answered by the routing section. If not, he will either: a) start a Github discussion thread about his question, and/or b) bring it to the agenda of next week's meeting. |
| 30 mins | Working Draft Feedback Review | Continue review of feedback on the Working Draft. NA/EU: We were able to review comments between sections 3 and 6. APAC: We ran out of time to do any spec comment review. | |
| 5 mins |
| Chairs | IMPORTANT: The TSPTF, Trust Registry TF, and X.509 VID TF all need to coordinate on which agenda we will use for the combined APAC meetings on Wednesdays 18:00-19:00 PT / Thursday 02:00-03:00 UTC. |
| APAC |
...
| Time | Agenda Item | Lead | Notes | ||
| 3 min |
| Chairs |
| ||
| 2 min | Review of previous action items | Chairs | CONSOLIDATED MEETING NOTES | ||
| 5 mins | Trust Registry Task Force | Major work conducted on moving specification over to
WORK/ASSISTANCE:
| 10 mins | Term for |
Screenshots/Diagrams (numbered for reference in notes above)
#1
...
#2
...
#3
...
Decisions
- DECISION: At least through the Implementers Draft, in the TSP spec, we will continue to use the term "relationship" or "VID relationship" when referring to the VID-to-VID
...
...
...
...
- Review decisions/action items
- Planning for next meeting
...
Screenshots/Diagrams (numbered for reference in notes above)
#1
#2
#3
#4
#5
#6
#7
#8
#9
#10
Decisions
- Sample Decision Item
Action Items
- Sample Action Item
- graph edge (in a graph theory sense). We will continue to test that terminology to see if any adjustment or additional terms (such as those related to the concept "sessions") are needed.
Action Items
- ACTION: Drummond Reed to draft a callout paragraph for the spec that explains why we are using the term "relationship" and not "connection" or "channel".
- ACTION: Tahoe Blue to review the Working Draft to determine if his question is answered by the routing section. If not, he will either: a) start a Github discussion thread about his question, and/or b) bring it to the agenda of next week's meeting.