Meeting Date & Time

Jan 9, 2025 This Task Force meets weekly every Thursday/Friday. It alternates between two times to maximize global coverage:

NA/EU Meeting: 10:00-11:00 PT / 13:00-14:00 EDT / 18:00-19:00 UTC / 19:00-20:00 CET / Friday 01:00-02:00 AEST
APAC Meeting: 14:00-15:00 PT / 17:00-18:00 EDT / 22:00-23:00 UTC / 23:00-24:00 CET / Friday 09:00-10:00 AEST

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

Zoom Meeting Recordings

NA/EU Meeting: NO RECORDING IS AVAILABLE FOR THIS MEETING DUE TO CALENDAR DIFFICULTIES (the meeting was moved to a different time slot before the calendar was updated).

Attendees

@Mathieu Glaude

@Scott Perry

@Jesse Carter

@Drummond Reed

@Markus Sabadello

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	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	ACTION: @Scott Perry and @Drummond Reed to get a copy of the ISO spec for LEIs in X.509 certificates. ACTION: @Drummond Reed will create a Doodle poll to find the best new meeting time slot for the NA/EU meeting. ACTION: @Drummond Reed to put assigning editors and developing a workplan for the HA VIDs spec on the agenda for the next meeting.
15 mins	Appoint Spec Editors	Chairs	Who wants to lean in to be a spec editor? DECISION: @Jesse Carter volunteered to be one of the spec editors. Drummond shared that had confirmed over the break that @Alex Tweeddale is also willing to be an editor. So that would give us a two-person editor team that can cover both the NA/EU and APAC calls. ACTION: @Jesse Carter to connect with @Alex Tweeddale offline to discuss: a) editing tools, b) proposed name of the spec, c) proposed structure of the spec (“strawman”), d) workplan / work assignments for producing a first Working Draft. If possible, bring the outcome of that offline discussion to next week’s APAC meeting.
25 mins	Structuring the spec and the work	All	How should we structure the spec and break up the work? How long should we give ourselves (realistically) to have a full Working Draft? We talked about the essence of what the spec needs to cover. Several options were discussed: Defining individual “bridges” between identifier pairs. Defining how to produce a “cryptographic synonym proof” for each type of identifier that can then be used to prove synonymity with another identifier if each cryptographic synonym proof points to an identifier in the other one. Creating a “high assurance bridge service” that actually does the work. Markus brought up the option of treating each method of producing a cryptographic synonym proof as a DID method. Then a DID resolver, given two DIDs, could do the work of resolving them, obtaining the cryptographic synonym proofs, verifying them, and finally comparing them to prove that they are synonyms (or not).
10 mins	Other topics
5 mins	Review decisions/action items Planning for next meeting	Chairs

Decisions

DECISION: @Jesse Carter volunteered to be one of the spec editors.

Action Items

ACTION: @Jesse Carter to connect with @Alex Tweeddale offline to discuss: a) editing tools, b) proposed name of the spec, c) proposed structure of the spec (“strawman”), d) workplan / work assignments for producing a first Working Draft. If possible, bring the outcome of that offline discussion to next week’s APAC meeting.