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: Wenjing Chu to work offline with Sam Smith to decide about the code values that need to be added to the CESR code table to support Sealed Box in section 9.2.2 of the spec (per issue #9).
  
  

25 mins

TSP and the new Decentralized Trust Graph Working Group

@Drummond Reed

Drummond will cover the charter for this new WG & lead a discussion about how it will build on TSP & the ToIP stack. The charter is:

The scope of the Decentralized Trust Graph Working Group (DTGWG) is to define the socio-technical standards for a decentralized trust graph (DTG) where there is no centralized database and all parties control their own subgraph of trust relationships. This work includes specifying requirements for interoperability, portability, security, privacy, and agency of DTG key management and recovery, verifiable identifiers, verifiable credentials, verifiable relationship credentials, social vouching, relationship cards (r-cards), privacy-preserving zero-knowledge proofs, trust task protocols, trust registries, out-of-band introductions, UI/UX affordances, decentralized naming and discovery mechanisms, and governance considerations. This work will be based on the Design Principles for the ToIP Stack, the ToIP Technology Architecture Specification, and other ToIP technical specifications. It will also align with existing decentralized identity (DID), verifiable credentials (VC), and federated networking standards to ensure broad compatibility and adoption across Web3 and decentralized social networking protocols such as Activity Pub, AT Protocol, NOSTR, and future social ecosystems.

Update on the KERI Stack and TSP

@Sam Smith

Sam reported that there are CESR version codes in CESR V2. So you can interleave versions of CESR. There are also 3 different group codes. This will enable the parser to parse CESR V2 messages.

See screenshots #1 and #2.

This is moving towards leveraging the abilities of a streaming protocol.

Sam added a payload type that explicitly distinguishes a control message. The payload is a sniffable CESR stream, which could be another CESR payload.

The other improvement is how SAIDs are being used in the relationship formation section of the spec.

All of this is covered in this GitHub issue. Sam walked us through it.

The first area covered was VID codes, covering all types of VIDs.

Sam noted that CESR encoding includes packet length padding so that correlation on packet length can be defeated.

25 mins

Review of Rev 2

@Wenjing Chu @Sam Smith

See the issues list. Wenjing walked us through the key changes that he has been making to the spec for Rev 2.

The main changes were in the section called Control Messages. These are specific messages used for creating relationships. It covers each of the required message types for creating relationships and the different supported mode for the cryptographic schemes.

The section called Serialization and Encoding is where the details about CESR encoding are captured. In Rev 2, there is no longer VID types, just a VID_String that can be either a URI or URN. See screenshot #3.

The next part is the TSP Payload Encoding. Some objects are for control purposes and some are payloads. Also, some may be in plaintext and some are in ciphertext. All fields are required even they are empty. Sam noted that this saves the need for labels, as the order is fixed, so it is much more compact.

Wenjing then covered the basic TSP payload types (screenshot #4) and higher layer payloads (screenshot #5).

Sam pointed out that with CESR self-framing, the code tells the parser how to parse the rest of of that frame.

Wenjing covered padding, which has not changed.

Wenjing still has work to do on the Nonce field; he wants to explore using SAIDs.

He then covered the Ciphertext coding section with the three algorithm types.

He also covered nesting payloads and routed payloads (screenshot #6). Sam noted that there are 3 different ways to handled nested payloads. They allow for both TSP-only messages and mixed messages. Wenjing asked about the benefits of the other two options (that are not currently covered in the spec). Sam clarified that you can use the X-control payload messages for that.

5 mins

• Review decisions/action items

• Planning for next meeting 

Chairs

@Drummond Reed shared that he is leaving next week on 7 weeks of personal travel and will not be able to chair any meetings until his return.