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

Leads

Link to spec: https://docs.google.com/document/d/1BVmciUxNsolRMknz3dws0dgYFfgwKLOTHRKuVb-Vazo/edit?tab=t.0#heading=h.u9t084b0ygnz

~ 5 mins

OID registration process

Move this to next meeting -tbc @Scott Perry

~ 20 mins

Focussed discussion on X.509 to DID bridge and the different ways this could be done, review Alex’s idea in the spec

Tim

• Add digest over the DIDDoc question, like a docker image

• We are almost reinventing message authentication codes (MACs)

• 1. Mapping can be single value

• 2. Mapping can be a one to many relationship

• 3. Mapping at a point in time is reflected by a digest

• Leaning towards SAN

Jo and Tim

• Getting into the weeds of the DIDDoc isn’t worth the effort, but an acknowledgement may be enough

Jesse

• SAN can be an array - one to many relationship

~ 30 mins

Review current state of spec AND updates made by Alex & Jesse

 Needs to be some type of challenge/response

• The signed mapping /relationship is unequivocal. Leading up to this signed mapping - there may be additional safeguards/gov mechanisms put in place. However, those are management/gov issues not technical issues. It is up to the issuer on how to decide that. We’re just scoping out the unequivocal mechanism of how the bridges connect

• The syntax needs to be unequivocal, the semantics is not for us to decide

• REQUIREMENT For an X.509 to relate to a DID, the DID must assert control over the same keypair. The entity is the controller over the key pairs on both sides. 

• Potential for a section of the DIDDoc verification relationship called “bridgeMethod”

5 mins

• Assign homework for attendees to fill out sections in more detail using the “cryptographic bridge” and “non-cryptographic bridge” structure

Leads