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

Compare with Current View Page History

« Previous Version 3 Next »

Meeting Date & Time

This Task Force meets every other Thursday. There are two meetings to serve different time zones:

  • NA/EU meeting: 08:30-09:30 PT / 16:30-17:30 UTC
  • APAC meeting: XX:00-XX:00 PT / XX:00-XX:00 UTC

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

Zoom Meeting Links / Recordings

  • NA/EU Meeting:  Zoom meeting link
  • APAC Meeting:  <insert Zoom link from ToIP Calendar entry here>

NOTE: These Zoom meeting links will be replaced by links to recordings of the meetings once they are available.

Attendees

NA/EU:

APAC:

  • ...

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
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 minReview of previous action itemsLeads
20 minsReview of prior art and suggested readings

Eric Scouten 

X.509 DID method: Decentralising PKI starting with a X.509 DID method (a presentation proposal for RWOT 9 in August 2019)

  • This is a call for a did:x509 method to exist as part of a transition from PKI to SSI, but is not a DID method spec.
  • I could not find any documentation of this dicussion occuring at RWOT 9. I did find evidence of further work on this topic by two of these authors. (See next item.)
  • The primary point of interest in this presentation proposal for me was the idea of further abstracting the method of X.509 certificate discovery by using submethods under their proposed did:x509 method.

Analysis of hybrid wallet solutions - Implementation options for combining x509 certificates with DIDs and VCs (a presentation proposal for RWOT 11 in 2022) and Combination of x509 and DID/VC for inheritance properties of trust in digital identities (presentation to Open Identity Summit, Bonn, 2022)

  • Eric Scouten to give these two papers a second reading, hopefully before Thursday meeting. They look very similar, thus the co-listing here. First impressions:
  • These papers talk about several possible methods for linking X.509 and DID identifiers, which again highlights that one of our larger challenges will be identifying the location of the X.509 cert.

did:x509 Method Specification (draft specification and sample code published by Microsoft, 2022)

  • Does not appear to be actively maintained. Published in October 2022, a few issues filed by author over next few months, but no further commits or public discussion that I could find.
  • Requires the X.509 cert to be placed in the signing envelope (i.e. in x5c header of JWS/JST documents).
  • Requires cert subject identity to be mirrored in the DID (example: 

    did:x509:0:sha256:WE4P5dd8DnLHSkyHaIjhp4udlkF9LqoKwCvu9gl38jk::subject:C:US:ST:California:O:My%20Organisation).

  • Allows Fulcio integration. (Fulcio is new to me. Can someone explain? Worth our time?)
  • Raises issue of which chain of trust to use (X.509 or VC).
  • Looks like a fairly good starting point for create/read operation specifications.

(Eric Scouten to read, hopefully before Thursday meeting)

15 minsTopic #2

15 minsTopic #3

5 mins
  • Review decisions/action items
  • Planning for next meeting 
Leads

Screenshots/Diagrams (numbered for reference in notes above)

#1


Decisions

  • Sample Decision Item

Action Items

  • Sample Action Item


  • No labels