2022-08-18 TATF Meeting Notes
Meeting Date & Time
Aug 18, 2022 This Task Force holds TWO meetings weekly every Thursday at the following times (to cover global time zones - see the Calendar of ToIP Meetings):
NA/EU 07:00-8:00 PT / 14:00-15:00 UTC
APAC 18:00-19:00 PT / 01:00-02: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 Meeting
@Drummond Reed
@Darrell O'Donnell <== On vacation
@Wenjing Chu <== On vacation
@Daniel Bachenheimer
@Neil Thomson
@Kevin Dean
@Tim Bouma
@Vikas Malhotra
@Judith Fleenor (Deactivated)
@thomsona
@Antti Kettunen
@sankarshan
@Steven Milstein
@isaac henderson
@Scott Perry
APAC Meeting
@Drummond Reed
@Judith Fleenor (Deactivated)
@Jo Spencer
@sankarshan
@Alex Tweeddale
@Dima Postnikov
Main Goals of this Meeting
1) Explain the new Google doc for the ToIP Technology Architecture Specification starting with Working Draft 03; 2) Review all the changes to sections 1-6 and the new Appendices in WD03, 3) Agree on the plan for this coming week.
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
3 min |
| Chairs |
|
5 min | Announcements | All | Updates of general interest to TATF members.
|
2 min | Review of previous action items | Chairs | ACTION: @Drummond Reed to add the ToIP Google Drive URL to the TATF Meeting Page template. ACTION: @Drummond Reed to implement the requirements numbering/compilation decision in the next Working Draft. ACTION: @Drummond Reed to incorporate Jo's "systems mental model" diagram and explanation into the next Working Draft. ACTION: @Drummond Reed to include a first draft of the "Current State Mapping" appendix in the next Working Draft. ACTION: @Drummond Reed to update @Darrell O'Donnell's proposed diagram per the feedback in the 2022-08-11 TATF meetings and then figure out where it best belongs in the next draft. ACTION: @Neil Thomson to create a first draft of a proposed three-dimensional "cube" diagram that can serve as an anchor to tie the different views of the stack. ACTION: @Drummond Reed to incorporate Neil's diagram into the next Working Draft. ACTION: @Jo Spencer to move a copy of his slide deck of 3 diagrams to the ToIP Google Drive for the TATF. |
| ToIP Technology Architecture Specification Review Topics |
| Discussion of progress on the working draft of the ToIP Technology Architecture Specification:
|
10 mins | NEW Google doc version of the spec (Working Draft 03) | @Drummond Reed | After our discovery last week that the Google doc we had been using for Working Drafts was not in the ToIP Google Drive, Drummond created a new Google doc that we will begin using now starting with Working Draft 03. However, Drummond was not able to consolidate all comments and suggestions on Working Draft 02 into Working Draft 03. So the instructions for the next few days only are:
ACTION: @Drummond Reed to complete consolidating the rest of the sections of Working Draft 02 into Working Draft 03. ACTION: @Drummond Reed to post to the |
5 mins | NEW Evolution of the ToIP Stack document | @Drummond Reed | In considering where and how to deal with the "Current State Mapping" diagram and explanation, the conclusion was that we should publish a companion living document that explains the whole process the ToIP Foundation is following in the development of the ToIP stack. See screenshot #1 (below). This resulted in small changes to sections 1 and 4. The concept now is to describe the purpose of this document (and a "hook" for reading it) in Appendix B. ACTION: @Drummond Reed to do his best to have a draft of this new Evolution of the ToIP Stack document ready for the ToIP Steering Committee meeting on Wednesday August 24. |
5 mins | Section 6.1: Design Goals | @Drummond Reed | See the revised list of four (previously three) relationship properties. Integrity has been added. |
5 mins | Section 6.2: The Four Layer Pattern | @Drummond Reed | @Darrell O'Donnell's diagram replaced the table we had used previously to illustrate the types of functions at various layers. See screenshot #2 (below). @Antti Kettunen said that with his "fresh eyes" looking at this section, it could use some additional explanation. ACTION: @Antti Kettunen to propose some additional revisions to section 6.2. |
5 mins | Section 6.3: High Level System Architecture | @Drummond Reed @Jo Spencer | @Jo Spencer's diagram has been added. See screenshot #3 (below). Also, a fourth type of interaction has been added (at @SUMABALA NAIR's suggestion): Intermediary System to Intermediary System.
APAC: We discussed some of the comments that have been added to this section in Working Draft 03, plus Jo's thoughts on the revisions to his diagram (screenshot #3). ACTION: @Jo Spencer to propose additional revisions to section 6.3. |
10 mins | Section 7.1: Requirements numbering & linking | @Drummond Reed | Appendix A now includes a table of requirements that is simply a placeholder at present—only the very first requirement is synced with the spec (to show how it should work). ACTION: @Drummond Reed to finish updating and cross-linking the requirements table in Appendix A once Working Draft 03 is complete. |
5 mins | Plan for the coming week |
| ACTION: @Neil Thomson to complete preparation of the Use Cases table to place into section 5 to complete Working Draft 03 by next week's meeting. ACTION: ALL to review sections 1-6 in Working Draft 03 and make any comments or suggestions. |
5 mins |
| Chairs |
|
Screenshots/Diagrams (numbered for reference in notes above)
#1
#2
#3
Decisions
None
Action Items
#tswg-tech-arch-tf channel on Slack as soon as he has consolidated the rest of the sections from Working Draft 02 into Working Draft 03.