You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Meeting Date & Time

  •   This Task Force holds TWO meetings weekly on Thursdays at the following times (to cover global time zones):
    • 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

Attendees

NA/EU Meeting

APAC Meeting

Main Goals of this Meeting

1) Review proposed revisions to the ToIP Technology Architecture Specification section 4 to add a more detailed definition of the purpose and expected outcomes, 2) review a consolidated list of the core terms and normative requirements prepared during the collaboration sessions earlier in the week.

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
3 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:
5 minAnnouncementsAll

Updates of general interest to TATF members.

Tim Bouma Digital Assets Consultation paper - has relevance for Layer 1, 2. Identity from a legal perspective (warning 500+ pages)

2 minReview of previous action itemsChairs
  • ACTION: ALL MEMBERS to continue to review sections 7 through 11 of the ToIP Technology Architecture Specification to add any final comments or suggestions.
  • ACTION: Drummond Reed to raise an GitHub on this topic as it will require more in-depth discussion that is feasible in Google docs (and because we are now trying to move all new issues to GitHub).

TAS REVIEW

Discussion of progress on the working draft of the ToIP Technology Architecture Specification:

15 minsReview proposed revisions to section 4

See this Google Doc for proposed revisions to section 4 that add a more detailed definition of the purpose and expected outcomes, including two parallel tracks for development of component specifications and interoperability profiles/test cases.

  • Make comments and suggestions in the doc

Neil Thomson Suggest that (top) TAF use cases are expanded in component specifications, then again for interoperability profiles/test cases. This provides spec traceability.

Darrell O'Donnell to suggest a replacement for Figure 2 (development progression)

Actions:

  • @NeilThomson - update dev prog and/or design principles to include "detailing" of Use cases from Tech Arch through test cases.
  • All - how do we number (normative) requirements, how to embed within the Tech Arch Spec (links to appendix)

General issues

  • Everyone has a Layer 1, 2, etc. Need to rename or make ToIP specific
  • What are "normative requirements" vs. "design principles" (e.g. "spanning layer")
30 minsReview a consolidated list of core terms and normative requirements

See this Google Doc for a consolidated list of the core terms and normative requirements coming out of the San Jose collaboration sessions earlier this week. 

5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

Note: Drummond Reed is on vacation until August 8th.

Screenshots/Diagrams (numbered for reference in notes above)

#1

Decisions

  • Sample Decision Item

Action Items

  • Sample Action Item


  • No labels