...
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
3 min |
| Leads |
|
15 min | Continuance of discussion regarding Mathieu’s Slack message | Leads | From yesterday’s discussion and some follow-up conversations I had afterward, it seems that our main goal is to draft a recipe for bridging a DID to DNS and any x509. This would be highly valuable and could gain momentum quickly. According to Jesse, who was a key driver behind the HA DIDs with DNS work, the technical aspect should be fairly straightforward. It’s essentially a matter of signing an identifier and placing it within the DID Doc, x509, or DNS domain. Since we’re simply providing the methodology for bridging trust realms, we are not in a position to address risk or assurance. All assurance-related processes are managed by third parties. Given this, one of the first steps we should take is to rename this task force to better reflect its purpose. Antti: we could align the High Assurance VIDs with the wallet eAddress work in the EU: https://github.com/a-fox/eudi-wallet-papers-and-discussions/tree/main/eAddress Tim and Jesse worked on the High Assurance DNS spec with SVIP DHS. Core problem is not from X.509, the problem with the key is having a high assurance binding with a human readable identifier and being able to resolve it to the associated cryptographic material. did:web is convenient. DHS trust architecture: https://dhs-svip.github.io/requirements-for-decentralized-identity/TrustArchitecture/
Draft RFC to be moved through IETF governance (need to decide which WG is best fit) |
15 min | Review of initial draft specification skeleton | Leads |
|
15 min | Allocation of sections for attendees to work on | Leads |
|
10 mins | Decision to be made on timelines for IIW announcement | Leads |
|
5 mins | Decision to be made on cadence of meetings going forward | Leads | |
5 mins |
| Leads |
|
...