Meeting Date & Time

Jan 10, 2024 This Task Force meets every Wednesday. There are two meetings to serve different time zones:

NA/EU meeting: 08:00-09:00 PT / 16:00-17:00 UTC
APAC meeting: 18:00-19:00 PT / 02:00-03:00 UTC

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

Zoom Meeting Recordings

Attendees

NA/EU:

@Drummond Reed
@Wenjing Chu
@Sam Smith
@Darrell O'Donnell
@Tim Bouma
@Charles Lanahan
@Rob Aaron
@Eric Drury
@Philip Feairheller
@Steve McCown
@Viky Manaila
@Judith Fleenor (Deactivated)

APAC:

@Darrell O'Donnell
@Judith Fleenor (Deactivated)
@Jo Spencer
@Ed Eykholt

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	Leads	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	Leads	ACTION: @Sam Smith and @Wenjing Chu to have an offline discussion on the topic of protocol versioning and come up with a proposal to add to the Working Draft. Carried forward. ACTION: ALL TSPTF MEMBERS to try to complete a full read-through of the Working Draft and add any comments prior to our next meeting on January 10.
20 mins	Update on Working Draft progress	@Wenjing Chu	Check-in to see how close we are to an Implementer's Draft. Key updates: Section 5 was moved. Wenjing started on sections 9 and 10 to provide at least enough for implementers to get started. In particular, we need to explain at least the basic transport protocol binding options, and also refer out to CESR. Wenjing said that he's had a chance to talk to some developers interested in implementation and they are relatively satisfied.
5 mins	Proposed VID/DID/SCID diagram	@Darrell O'Donnell @Drummond Reed	Over the break, Darrell created the diagram in screenshot #1 below. We are proposing to use this as the replacement for Figure 6 in section 6.4 of the ToIP Technology Architecture Specification. This led to a long discussion about VIDs, the meaning of cryptographically verifiability, appraisability, and the tradeoffs of "big tent" vs. high assurance. The result was two design decisions (which still need consensus on the. APAC call): DECISION: Section 3 of the TSP spec, Verifiable Identifiers, will be the "mini-spec" for VIDs, including the ABNF. We will not break it out into a separate specification because it is so integral to the TSP (just as the spec for IP addresses was integral to the Internet Protocol specification). DECISION: Our baseline approach to VID appraisability will be an optional `VID type property` that a verifier can use in conjunction with the VID value to make a baseline trust decision about the VID. In addition, to enable extensibility, the VID ABNF should also allow any URN, which includes DIDs.
15 mins	Feedback on the current Working Draft	ALL	Review comments from TF members who found time to review the Working Draft over the holiday break (including the Slack threads). We ran out of time to discuss any comments outside of the VID discussion above. ACTION: @Drummond Reed to add "Spec Feedback Review" to the agenda for next week's meeting.
10 mins	Preparation for a Implementer's Kickoff Meeting	Leads	If we are close enough, discuss the preparations we should make for holding an Implementer's Kickoff Meeting. How much lead time should we provide? How much should be covered in a blog post? Wenjing felt that it was realistic for us to be ready within 3 meetings, i.e., by the end of January. ACTION: @Drummond Reed to add "Prepare for Implementers Kickoff Meeting" to the agenda for the next meeting.
5 mins	Review decisions/action items Planning for next meeting	Leads

Screenshots/Diagrams (numbered for reference in notes above)

#1

#2

From Ed Eykholt — TSP Class Diagram

Decisions

DECISION: Section 3 of the TSP spec, Verifiable Identifiers, will be the "mini-spec" for VIDs, including the ABNF. We will not break it out into a separate specification because it is so integral to the TSP (just as the spec for IP addresses was integral to the Internet Protocol specification).
DECISION: Our baseline approach to VID appraisability will be an optional VID type property that a verifier can use in conjunction with the VID value to make a baseline trust decision about the VID. In addition, to enable extensibility, the VID ABNF should also allow any URN, which includes DIDs.

Action Items

ACTION: @Sam Smith and @Wenjing Chu to have an offline discussion on the topic of protocol versioning and come up with a proposal to add to the Working Draft.

ACTION: @Drummond Reed to add "Spec Feedback Review" to the agenda for next week's meeting.

ACTION: @Drummond Reed to add "Prepare for Implementers Kickoff Meeting" to the agenda for the next meeting.