2025-02-19 TSPTF Meeting Notes

2025-02-19 TSPTF Meeting Notes

Meeting Date & Time

Feb 19, 2025 This Task Force meets every other Wednesday. There is a single meeting for the NA/EU. (Updates for the APAC time zone will be at the monthly TSWG APAC meeting the first Tuesday of every month.)

  • NA/EU meeting: 08:00-09:00 PT / 16:00-17:00 UTC

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

Zoom Meeting Recording

Attendees

  • @Drummond Reed

  • @Sam Smith

  • @Daniel Bachenheimer

  • @Neil Thomson

  • Nicholas Racz

  • @Eric Drury

  • @Steven Milstein

  • @Wenjing Chu

  • @Rob Aaron

Agenda Items and Notes (including all relevant links)

Time

Agenda Item

Lead

Notes

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.

  • NOTICE: In addition to the licensing terms of this Working Group’s JDF charter, this Working Group operates under the official policy that any Working Group Participant who makes a contribution to a Draft Deliverable shall have a maximum of 45 days from the date of that contribution to exclude any Essential Claims pertaining to that contribution.

  • New Members:

2 min

Review of previous action items

Chairs

ACTION: @Sam Smith to add a pointer in issue #44 to the precise places in the referenced KERI spec.
ACTION: @Sam Smith to review the current spec to suggest what CESR codes are needed in the relationship formation portion of the protocol.
ACTION: ALL TF MEMBERS review and comment on existing issues or add new issues as needed. 

15 mins

DID SCID Method

@Drummond Reed

A new TSWG task force has been proposed to create a family of DID methods based on self-certifying identifiers (SCIDs). This method is especially interesting for peer-to-peer applications using trust tasks over TSP.

Because the DID SCID method does not actually define a specific new DID method, but rather a class of new DID methods that use SCIDs, @Wenjing Chu suggested that the best way to describe it was as a metamethod. @Drummond Reed agreed.

ACTION: @Drummond Reed to update the Introduction section of the DID SCID Method Specification to use the term "metamethod".

30 mins

Open Issues

Chairs

See the action items above and the issues list.

We started on issue #44 in section 9.2 discussing the mapping table.

@Sam Smith posted a comment to the original Google doc of the TSP Spec. See screenshot #1.

Sam and Wenjing had a long discussion about the enveloping of the protocol and the efficiency of parsing. 

ACTION: @Wenjing Chu will work on issue #44. 

We also briefly discussing issue #45, recursive hops in issue #43.

We agreed issue #9 on CESR encoding still needs to be resolved.

Issue #14 is also on the list.

Also issue #12 on Security and Privacy Considerations.

Sam also proposed the principle that all parsing should be table-based to maximize efficiently.

ACTION: @Wenjing Chu will add an label for all issues that we want to close for the Implementers Draft 02.

5 mins

Interop testing

All

Wenjing asked about interoperability testing. His suggestion is that we should aim for alignment of implementations on Implementers Draft 02, and then we can perform interop testing on the basis of that draft.

5 mins

  • Review decisions/action items

  • Planning for next meeting 

Chairs

 

Screenshots/Diagrams (numbered for reference in notes above)

#1


#2


Decisions

  • None

Action Items

ACTION: @Drummond Reed to update the Introduction section of the DID SCID Method Specification to use the term "metamethod".
ACTION: @Wenjing Chu will add an label for all issues that we want to close for the Implementers Draft 02.
ACTION: @Sam Smith and @Wenjing Chu to work on alignment of CESR table codes to resolve several current issues.