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.

• New Members:

2 min

Review of previous action items

Chairs

None

30 mins

Review of new Spec-Up version of the current Working Draft

@Wenjing Chu 

Here is a link to the rendered version of the Spec-Up Markdown. This version is currently in Wenjing's fork of the repo as he is still cleaning up the transformation from Google docs to Spec-Up.

We discussed the multi-cast section and agreed that we will write something there but that we haven't decided yet.

We discussed key rotation and whether it should happen at the TSP layer.

@Sam Smith shared that he believes doing key rotation at the TSP layer is a layer violation. It should be a separate layer. KERI solves it with a specific message type.

@Darrell O'Donnell agreed that it should be a separate trust task protocol.

Wenjing asked if there should be a message to request a "key check" message.

ACTION: Wenjing will add a defined message to the relationship formation stage which can be used to notify another party of a key state change.

We discussed the Security and Privacy Considerations sections. Wenjing said that for the Implementers Draft, he plans to start compiling suggestions for those sections but not to try to fully draft them. Drummond said that this is one place where implementors can often make valuable suggestions.

10 mins

Final steps to publishing an Implementers Draft

Chairs

We discussed the need to publish a new blog post announcing an Implementers Draft.

There is a ToIP wiki page with guidance on this topic.

@Judith Fleenor (Deactivated) explained the enhancements to the process of publishing a specification and the associated blog post.

ACTION: @Drummond Reed will prepare a first draft of a blog post announcing the TSP Implementers Draft by our April 3 meeting.

10 mins

TSP Implementations

All

Wenjing said that he's prepared to do a demo of a Rust implementation at IIW as a way of showing the protocol already working.

He is very interested in showing different VIDs working with it. @Sam Smith said that he would interested in showing it working with AIDs.

Wenjing asked for input about having that open source implementation at OWF. @Drummond Reed and @Darrell O'Donnell were favorable about doing that.

@Darrell O'Donnell shared his view that the code that best belongs at ToIP is test suites.

ACTION: @Judith Fleenor (Deactivated) to seek a ToIP Steering Committee policy decision about whether to encourage (or require) ToIP Foundation code projects to be limited to test/conformance suites.

5 mins

• Review decisions/action items

• Planning for next meeting 

Chairs