Meeting Date & Time
-
- NA/EU 07:00-8:00 PT / 15:00-16:00 UTC
- APAC 1:00-2:00PM PT / 21:00-22: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
- Drummond Reed
- Darrell O'Donnel
- Neil Thomson
- Phil Feairheller
- Antti Kettunen
- Wenjing Chu
- Goutam Sinha
- Isaac Henderson
- Kevin Dean
- Kevin Griffin
- Tim Bouma
- Rodolfo Miranda
- sankarshan
- Vikas Malhotra
- Judith Fleenor
APAC
Main Goal of this Meeting
1) Discuss the recent FIDO white paper. and any implications for the ToIP stack, 2) continue discussion of feedback on the storyline deck of layer-by-layer requirements.
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
5 min |
| Chairs |
|
5 min | Announcements | All | Updates of general interest to TATF members.
|
5 min | Review of previous action items | Chairs |
|
15 mins | The KERI / ACDC "stack" | Phil Feairheller | Per the first action item above, Phil shared a diagram (screenshot #1 below) of how all the component pieces/specs for KERI and ACDC fit within the four-layer ToIP stack. (This diagram is now part of the ToIP Protocol Stack Diagrams Google Slides deck.)
|
15 mins | FIDO white paper discussion | Continue a discussion that started on the ToIP Slack about the recent FIDO white paper. Wenjing Chu posted this: There’s a lot to learn here. I’d like to highlight one - we need a proper mental road map for the development of a complex ToIP stack. AKA a life cycle model. Reactionary mode can be exciting but ultimately not most productive.
DECISION: The TATF shall develop a roadmap for the evolution of the ToIP stack, a summary of which should be included as a section in the ToIP Technology Architecture Specification V1, in order to make it clear what are the canonical use cases and scope limitations for the V1 ToIP stack. ACTION: Drummond Reed to make the first agenda item for next week's meeting a discussion of the canonical use cases and scope limitations for the V1 ToIP stack. ACTION: Drummond Reed to start a discussion on our Slack channel about the canonical use cases and scope limitations for the V1 ToIP stack in preparation for next week's meeting. | |
20 mins | Continue review of comments on requirements | All | Continue our review of requirements in the storyline deck of layer-by-layer requirements. Our goal is to move into drafting the Google doc version of the spec next week. (All slide numbers are of 2022-03-31).
ACTION: Drummond Reed to prepare a revised outline of the Google doc version of the ToIP Technology Architecture Specification for review at next week's meeting. |
5 mins |
| Chairs |
Screenshots/Diagrams (numbered for reference in notes above)
#1
Decisions
- DECISION: The TATF shall develop a roadmap for the evolution of the ToIP stack, a summary of which should be included as a section in the ToIP Technology Architecture Specification V1, in order to make it clear what are the canonical use cases and scope limitations for the V1 ToIP stack.
Action Items
ACTION: Drummond Reed to make the first agenda item for next week's meeting a discussion of the canonical use cases and scope limitations for the V1 ToIP stack.
ACTION: Drummond Reed to start a discussion on our Slack channel about the canonical use cases and scope limitations for the V1 ToIP stack in preparation for next week's meeting.
- ACTION: Drummond Reed to prepare a revised outline of the Google doc version of the ToIP Technology Architecture Specification for review at next week's meeting.