Meeting Schedule
- Bi-Weekly at 8:00-9:00 am PDT / 11:00-12:00 am EDT / 15:00 – 16:00 UTC / 17:00 - 16:00 CEST
Attendees
- Eric Drury
- Carly Huitema
- Feng Hou
- Charles Lanahan
- Drummond Reed
- Neil Thomson
- Scott Whitmire
- Jordan Evans
- Darrell O'Donnell
- Steve Magennis
- Judith Fleenor
- Stephen Curran
Main Goal of this Meeting
We're using this week's EFWG meeting to give the floor to anyone who'd like to give an update on IIW.
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
5 min |
| Chairs |
|
1 min | Announcements | TF Leads | News or events of interest to EFWG members: |
5 min | Review of action items from the previous meeting | Chairs | Bhutan NDI Case Study update |
40 min | IIW Recap | All | Sessions or content that we'd be interested in hearing about:
|
5 min |
| Chairs |
Recording
Notes
AI notes
TDW - Trust DID Web is a new DID method but doesn't get DID doc from HTTP location but instead you get a log of all the entries of the changes of the DID doc. Every line is tied to the previous via a hash of the entry. The controller determined according to DID spec who much sign every transition. Very similar to DID: webs, but the difference is the transition state is the DID doc. Can you pre-rotation of keys. Next step, take the spec to a task force to evolve the specification. This DID has portability that lets you move the location of the DID, this changes the DID but the SCID (self certifying identifier) plus the history stays the same. Combine with high assurance DNS as with DID:webs will work the same. Long term storage - 30yr+, what kind of archival storage for this information?
DID:web is becoming well used but it really lasts history verifiability and this specification (TDW) adds ledger based features without a ledger but still fits very well with DID:web.
Comparison to DID:webs - DID:webs is KERI focused with a side of DID. But DID:tdw is DID focused and has less complexity compared to KERI and DID:webs.
DID:webs - uses KERI to take you state to state, you have to go further to generate a DID doc, requires more complexity to fit within the DID standard specification. The implication is that DID:tdw is easier from an adoption standpoint.