Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

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

Attendees

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:

20 min

Review of previous action items

Chairs

  • ACTION: Alex Tweeddale and Jesse Carter to present outcomes of discussion on:
    - editing tools
    - proposed structure of the spec
  • - Standardised pointer structure: As we go through the exercise of putting the initial MVP identifiers together, it will hopefully expose an underlying pattern of structure which we can then use to build out a model that we can share with other ecosystems
  • - Proposed idea, start with a “Minimum viable” set of identifiers - DIDs, X.509 and DNS which then we can iterate out from afterwards
    - work assignments to achieve first draft

10 mins

Open discussion points from previous NA/EU meeting

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:

  1. Defining individual “bridges” between identifier pairs.

  2. 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.

  3. 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).

15 mins

Assignment of work items for spec first draft

All

 

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.

  • No labels