Page Comparison

• 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:
  • Kalin has been in CBDC for years, a longtime member of ToIP, but now mostly advising governments about decentralized identity and credentials—with a focus on interoperability.

Wenjing started by showing screenshot #1 below to get feedback on the terminology it uses.

Feedback was that the diagram could also included the term "message" at the bottom to clarify that a TSP message consists of the envelope + payload + signature.

The other feedback is that the diagram is so helpful in terms of a visual overview of what the spec covers that it would be very helpful to have it included in the spec.

Ed Eykholt had questions about how all of the following would be handled:

• broadcast (multiple receivers?)
• routing
• attachments  (multiple signatures)
• tunneling  (message composition), perhaps recursion

Wenjing clarified that the diagram is a "test vector" diagram that shows one way that the protocol can be used. He said all of Ed's questions/examples could be covered by other test vectors that could all be included in an appendix.

Drummond Reed suggested that Ed start one or more GitHub discussions that discuss questions about each test vector.

Wenjing Chu 

We discussed VID encoding. We had agreed to have a VID type, which means we need a VID type code table. If we have a four character type code, then the first character indicates that it is a type code, and the next 3 characters are the code. That gives us a code space of 18 bits (2 to the 18th), which should easily be large enough.

Sam Smith proposes that a null type code would mean the VID is a URN.

We discussed the pluses and minuses of having a type code table. We agreed that we will need to have a governance mechanism.

APAC:

Wenjing explained that our concept of VIDs allows for some flexibility BUT wants to avoid the explosion of options that has happened with DID method. The solution is by creating a CESR code table for VIDs. That is how we can define a set of policies that a VID type must meet in order to be registered for that code table. We can also allocate a portion of that code table bit space to "experimental" codes to allow for market-driven innovation.

We reviewed the first draft blog post proposed by the ACDC TF for public review of their suite of specifications. There was a discussion about the dependencies between these three specifications. Darrell O'Donnell drew the following diagram suggesting the relationships. 

ACTION: Drummond Reed and Darrell O'Donnell to have a discussion with the ACDC leadership about the length of the public review and the depth of the announcement blog post.

Darrell O'Donnell Eric Scouten