Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

Version 1 Next »

Meeting Date & Time

This Task Force meets every other Wednesday. The first meeting (for the NA/EU time zones) is dedicated to the TSPTF. The second meeting, for the APAC time zones, is the joint weekly APAC meeting of all Task Forces in the ToIP Technology Stack Working Group.

  • NA/EU meeting: 08:00-09:00 PT / 15:00-16:00 UTC
  • TSWG bi-weekly APAC meeting: 18:00-19:00 PT / 01:00-02:00 UTC

See the Calendar of ToIP Meetings for exact meeting dates, times and Zoom links.

Zoom Meeting Links / Recordings

NOTE: These Zoom meeting links will be replaced by links to recordings of the meetings once they are available (usually by the end of the day of the meeting).

Attendees

<list here>

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
3 min
  • Start recording
  • Welcome & antitrust notice
  • New member introductions
  • 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:
2 minReview of previous action itemsChairs
  • ACTION: Drummond Reed and Wenjing Chu to coordinate with Judith Fleenor on scheduling two blog progress milestone blog posts: one in August about the OWF TSP milestone, and one right before IIW about a second Implementers Draft.

  • ACTION: Drummond Reed to schedule Wenjing Chu to give a OWF TSP project demo on the agenda for the next meeting on Sept 4th.

  • ACTION: Wenjing Chu and Sam Smith to get together offline to work on alignment of the CESR code points.

15 minsReport from the LF Decentralized Trust launch in Vienna

Wenjing Chu


15 minsVID typing proposalSam SmithA proposal to simplify the how a VID type is specified in a message so that we don't need to have a VID type registry.
15 minsCESR PayloadsSam SmithReview how payloads are specified in CESR. Sam believes that by better leveraging how a parser could parse CESR, we can use one packet format for all ESSR packets. All the variability will be in the payload. He believes this is not a big change as it just removes some options that can be handled at the CESR level rather than the TSP packet level.
5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

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


  • No labels