Skip to content

Latest commit

 

History

History
200 lines (163 loc) · 12.7 KB

agenda.md

File metadata and controls

200 lines (163 loc) · 12.7 KB
Raw

Trust DID Web Work Item Rolling Agenda

Zoom Link: https://us02web.zoom.us/j/83119969275?pwd=IZTuXgGLtdLPjPLuB6q8zHXazxHSsU.1

Agenda: HackMD, TrustDIDWeb Repository (synchronized after each meeting)

WG projects | DIF page | Mailing list and Wiki | Meeting recordings

Table of Contents

Meeting Information

Participants are encouraged to turn your video on. This is a good way to build rapport across the contributor community.

This document is live-edited DURING each call, and stable/authoritative copies live on our github repo under /agenda.md, link: Agenda.

Future Topics

  • Using the did:tdw log format with other DID Methods
  • Merging did:tdw features into did:web?
  • Implementor's experiences -- architectures, learnings
  • A did:tdw test suite -- such as proposed here

Meeting - 24 Oct 2024

Time: 9:00 Pacific / 18:00 Central Europe

Recording: Zoom Recording Link

Attendees:

  • Stephen Curran
  • And others...
  1. Welcome and Adminstrivia
    1. Recording on?
    2. Please make sure you: join DIF, sign the WG Charter, and follow the DIF Code of Conduct. Questions? Please contact operations@identity.foundation.
    3. did:tdw Specification license -- W3C Mode
    4. Introductions and Agenda Topics
  2. Latest spec updates and implementation notes.
    1. Cleaning up [[spec]] references -- Brian has enabled us to add our own spec references.
    2. Next up -- DRYing the. spec.
    3. Security and Privacy sections. Anyone able to help?
    4. Getting "spec to a standard" advice and applying those changes.
  3. Registering did:tdw as a DID Method PR, and adding a did:tdw component to the Universal Resolver.
  4. DID Linked Resources and did:tdw
    1. Mechanisms to publish/resolve files related to the DID -- e.g., AnonCreds objects, OCA Files, BitListStatus, etc.
    2. DID Linked Resources vs. relativeRef currently in the spec
    3. Complexity of DID Linked Resources is that the DLRs must be listed somewhere so they can be included in the DID Metadata that is part of the DID resolution result. 4. Use case: Clients of resolvers find a DID URL for the resources. With relativeRef there is the same DID-To-HTTPS transformation to get the resource as to get the DID Log/DID Doc. 5. Use case: A resource points to a sequence of related documents, as in the case of RevRegEntries in AnonCreds. One identifier, but multiple resources. How does one find (a) the latest, (b) the entire list of entries (c) a specific entry at a given time? Each of those features could be needed with RevRegEntries.
  5. Spec. PRs and Issues
    1. Issues that would be breaking changes -- close them?
  6. Update on the did:tdw Web Server -- Patrick St. Louis.
  7. Open Discussion

Meeting - 10 Oct 2024

Time: 9:00 Pacific / 18:00 Central Europe

Recording: Zoom Recording Link

Attendees:

  • Stephen Curran
  • Sylvain Martel
  1. Welcome and Adminstrivia
    1. Recording on?
    2. Please make sure you: join DIF, sign the WG Charter, and follow the DIF Code of Conduct. Questions? Please contact operations@identity.foundation.
    3. did:tdw Specification license -- W3C Mode
    4. Introductions and Agenda Topics
  2. Latest spec updates and implementation notes.
    1. Version 0.4 is out.
    2. https://didtdw.org/ site is published.
    3. Implementer's Guide, etc. removed from the spec
    4. Next up -- DRYing the. spec.
    5. Anyone know a "Spec Veteran" that would be willing to review and point out deficiencies and potential improvements in the spec? Especially one with W3C spec experience.
      1. Suggestion to wait on this until after the DRYing is done.
  3. Update on the did:tdw Web Server -- Patrick St. Louis.
  4. DID Linked Resources and did:tdw
    1. Should we? How?
  5. Spec. PRs and Issues
  6. Open Discussion

Meeting - 26 Sept 2024

Time: 9:00 Pacific / 18:00 Central Europe

Recording: Zoom Recording Link

Attendees:

  • Stephen Curran
  • Others...
  1. Welcome and Adminstrivia
    1. Recording on?
    2. Please make sure you: join DIF, sign the WG Charter, and follow the DIF Code of Conduct. Questions? Please contact operations@identity.foundation.
    3. did:tdw Specification license -- W3C Mode
    4. Introductions and Agenda Topics
  2. Feedback from implementing did:tdw Witness capability -- Brian Richter.
    1. Resolver has a /witness endpoint -- got the request from the DID Controller.
    2. Stuck on signing the entry. Both log entries have a did:key -- the witnesses must be published DIDs -- SHOULD be a did:tdw?
    3. Where to send the witness request? The DID Controller should know that.
    4. Perhaps add an endpoint for the witnesses in the witnesses object? Decided no -- not to include the endpoint since that puts too much definition in the specification on how to implement the DID Controller and Witness interface. It is left to the DID Controller and witnesses to decide how they will interact. All that is specified is that resolvers can verify the proofs via the DID referenced in the witnesses object, and the key identifier that references that DID in the proof itself.
    5. Use cases for witnesses -- (1) monitoring the DID controller to prevent maliciousness -- no backtracking, (2) preventing attacks on the DID Controller.
    6. Next steps -- Brian to continue implementing based on the discussion. Addition of weasel words to the spec to note the implementation challenges.
  3. Spec. update to switch from a DID log entry being a JSON array to an object. Feedback? -- Stephen Curran. Good to go with the names of the items in the object.
    1. General feedback -- all good.
    2. We reviewed the names and agreed with the ones in the PR now -- versionId, versionTime (both of which align with the DID Core spec query parameters), parameters, and state. proof is as defined in the DI specification.
  4. Proof Chain vs. Proof Set
    1. Semantics:
      1. Proof Chain implies that that a subsequent signature is added to an existing signature, implying an attestation of that signature. But there are no implementations of it that we know of, and it's inclusion adds complexity without the semantics giving much benefit in did:tdw.
      2. Proof sets are just independent proofs across the same data.
    2. For now, let's just go with proof sets, as there is little benefit from using proof chains.
  5. Update on the did:tdw Web Server -- Patrick St. Louis. 8. Demo given, but we ran out of time.
  6. DID Linked Resources and did:tdw
    1. Should we?
  7. Spec. PRs and Issues
  8. Open Discussion

Meeting - 12 Sept 2024

Time: 9:00 Pacific / 18:00 Central Europe

Recording: Zoom Recording Link

Attendees:

  • Stephen Curran
  • Dmitri Zagidulin
  • Cole Davis
  • Brian Richter
  • Andrew Whitehead
  • Sylvain Martel
  • Martina Kolpondinos
  • John Jordan
  • Patrick St. Louis
  • Jamie Hale
  1. Welcome and Adminstrivia
    1. Recording on?
    2. Please make sure you: join DIF, sign the WG Charter, and follow the DIF Code of Conduct. Questions? Please contact operations@identity.foundation.
    3. did:tdw Specification license -- W3C Mode
    4. Introductions and Agenda Topics
  2. Introduction to the did:tdw Work Item at DIF
    1. CCG Presentation on did:tdw (starts at the 5:40 mark of recording)
  3. Brief(!) introduction to did:tdw
  4. Discussion:
    1. What do you want this group to achieve?
    2. What would help you the most?
      1. Get to 1.0!
      2. Web server
      3. Next step topics -- witnesses, deactivation -- how does a diploma remain verifiable when the isssuer disappears -- with their web server. Aka durability.
      4. Acceptance of the method broadly.
      5. How did:tdw compares with KERI.
      6. Test suite!!!!! Implementation consistency.
      7. Cryptographic audit on the techniques used -- hashing use, etc.
      8. Governemnt acceptance of the cryptographic suites being used.
      9. Switchcord is running live use cases based on did:web -- would like to transition to did:tdw and its features.
  5. Feature list feedback document -- importance of features?
  6. Future Topics
  7. Next Meeting -- next week, same time
    1. Input to TPAC.
  8. Spec. PRs and Issues
  9. Action items and next steps:
    1. Stephen to create a PR to change the spec. to say that a version is an object, JSON Patch is no longer used, and that the Data Integrity Proof is across the version object, without a challenge.
    2. Everyone to look at the list of did:tdw features and comment on the features.
    3. Everyone to review issues and open others as needed, to drive future discussions.