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:

  • Kevin Triplett is an electrical engineer who gradually shifted from hardware to software, has dealt with everything from databases to front ends. Also a documentary filmmaker. Since his retirement, he’s been focused on collective decisionmaking. He’s at the intersection between “social tech” and “hard tech”. Feels that the TSP is in the critical path of what needs to be solved. Goal is to enable larger-scale decision making, but to be able to do that requires connecting many local decision makers more efficiently. Loves cryptography. Also worked in OT, safety systems and refineries.

  • Wenjing shared that his early thesis work was on traffic control on the Internet, so he was working with Internet protocols very early in his career.

  • Sam shared that he got a PhD in electrical engineering, then became an academic, working with DoD in machine learning and early stage of AIs, particularly in autonomous underwater vehicles and survivable shipboard automation. Retired and moved into cloud automation systems, but started to have a focus on security. Wrote several papers that birthed SSI and then the KERI protocol. Wrote a paper called SPAC — Secure Privacy, Authenticity, and Confidentiality — focused on the authenticity problem of security over the Internet, secondarily confidentiality, and thirdly the issue of surveillance and metadata privacy.

  • Carly Huitema has a PhD in microbiology, works in research data management at the University of Guelph, is interested in decentralized technologies and is working to create educational content about ToIP trust topics to make the concepts more accessible. https://www.youtube.com/hashtag/bitesizetrust

2 min

Review of previous action items

Chairs

None

10 mins

Proposal to switch into asynchronous work mode (no regular meetings, only special purpose meetings)

Chairs

PROPOSAL: With the TSP spec nearing the 1.0 level, the TSPTF shall move into asynchronous work mode, using our GitHub repo to coordinate on resolving issues and PRs, until the V1.0 spec is ready for finalization. The Decentralized Trust Graph Working Group will take over our Wednesday 15:00 UTC meeting slot, however they have agreed that TSPTF can reclaim that meeting slot whenever the TSPTF needs an in-person meeting (for all or part of the hour) provided TSPTF gives at least one week’s notice.

DECISION: The TSPTF will switch into asynchronous work mode, coordinating work items via our GitHub repo for the TSP spec, and only calling Zoom meetings when needed. We will give our current bi-weekly meeting slot to the new Decentralized Trust Graph Working Group but reserve the right to call a meeting in that slot with one week’s notice.

35 mins

Open Issues

Chairs

Review and closure of open issues. See the issues list.

We discussed issue #57. The conclusion was to use the dot value (e.g., the "xx" in 1.xx) in TSP protocol versioning for changes in code points. See the issue for additional comments.

Wenjing next brought up a question about the CESR count code: having to put the code in the prefix means that the encoder has to determine the size of the payload before it can write the count code in the prefix. He was wondering if there was a more efficient solution.

Sam explained that he was using with byte arrays in Python, and he can add the count code fairly efficiently. Wenjing pointed out that it adds to the load on the sender.

Sam said that the design principle of CESR was to support “core affinity” in data centers, i.e., that the parsing of a stream at a data center is the bottleneck, so being able to shunt of a part of a stream to a different core is a requirement.

Wenjing pointed out that the benefit of the count code matters the most if the receiver is not decoding in real time, but if the receiver is decoding in real time, the count code does not help.

Wenjing and Sam discussed that cryptographic verification can jump straight to the end to grab the signature, so that can be verified efficiently.

5 mins

Any other business

We shared the following links to implementation projects with Kevin to help him investigate TSP:

https://trustoverip.github.io/tswg-cesr-specification/

https://github.com/WebOfTrust Sam points to “cesride”.

https://github.com/openwallet-foundation-labs/tsp
Sam mentioned that Human Colossus also has a Rust implementation, but it is under a different license.

5 mins

• Review decisions/action items

• Planning for next meeting 

Chairs

No further bi-weekly meetings until we need one; at that point we just need to give a week’s notice.