Skip to content

agenda_2021.md

Latest commit

 

History

History
1394 lines (1176 loc) · 59.9 KB

agenda_2021.md

File metadata and controls

1394 lines (1176 loc) · 59.9 KB
Raw

DIF Identifiers & Discovery WG – Rolling Agenda & Minutes

hackmd-github-sync-badge

WG projects | DIF page | Mailing list and Wiki | Recordings

For this call, you are encouraged to turn your video on. This is a good way to build rapport given we are a large, disparate group experiencing a lot of churn.

This document is live-edited DURING each call, or shortly after the call, and stable/authoritative copies live on our github repo under /agenda.md . Please note that we might not notice a pullrequest in time, but you are free to propose agenda items for future meetings via hackmd.

Meeting information - Bi-weekly Mondays 1400 ET

Special Work Item Calls:

In addition to the regular I&D WG meetings, we also hold Work Item Calls dedicated to individual work items. Any work item lead can organize Work Item Calls about their work item.

did:webvh Work Item Call - Every second Thursday 0900 PT


This weekly Work Item Call is dedicated to the did:webvh work item. We discuss issues related to the specification, and how the Work Item could relate to other technologies.

Meeting page

Universal Resolver Work Item Call - Wednesdays 0800 ET (discontinued)


This weekly Work Item Call is dedicated to the Universal Resolver work item. We discuss policy and governance topics (e.g. when to add/remove drivers), as well as technical topics (e.g. integration with the W3C DID test suite, monitoring, analytics, etc.).

Meeting invite | Zoom room

  • Work Item Call - 19 May 2021 - (1300ET) recording
  • Work Item Call - 26 May 2021 - (1300ET) cancelled
  • Work Item Call - 02 Jun 2021 - (1300ET) recording
  • Work Item Call - 09 Jun 2021 - (1300ET) recording
  • Work Item Call - 16 Jun 2021 - (1300ET) recording
  • Work Item Call - 23 Jun 2021 - (1300ET) recording
  • Work Item Call - 30 Jun 2021 - (1300ET) recording
  • Work Item Call - 07 Jul 2021 - (1300ET) canceled
  • Work Item Call - 14 Jul 2021 - (1300ET) recording
  • Work Item Call - 21 Jul 2021 - (0800ET) recording
  • Work Item Call - 28 Jul 2021 - (0800ET) recording
  • Work Item Call - 04 Aug 2021 - (0800ET) summer break
  • Work Item Call - 11 Aug 2021 - (0800ET) summer break
  • Work Item Call - 18 Aug 2021 - (0800ET) summer break
  • Work Item Call - 25 Aug 2021 - (0800ET) summer break
  • Work Item Call - 01 Sep 2021 - (0800ET) recording
  • Work Item Call - 08 Sep 2021 - (0800ET) recording
  • Work Item Call - 15 Sep 2021 - (0800ET) canceled
  • Work Item Call - 22 Sep 2021 - (0800ET) canceled
  • Work Item Call - 29 Sep 2021 - (0800ET) recording
  • Work Item Call - 06 Oct 2021 - (0800ET) recording
  • Work Item Call - 13 Oct 2021 - (0800ET) canceled
  • Work Item Call - 20 Oct 2021 - (0800ET) canceled
  • Work Item Call - 27 Oct 2021 - (0800ET)
  • ...
DID Registration Work Item Call - Wednesdays 1100 CET (discontinued)


This weekly Work Item Call is dedicated to the DID Registration work item. We discuss scope and high-level architectural questions, work on the specification, and analyze other, related initiatives and specifications.

Meeting invite | Zoom room

  • Work Item Call - 19 May 2021 - (1000ET) recording
  • Work Item Call - 26 May 2021 - (1000ET) recording
  • Work Item Call - 02 Jun 2021 - (1000ET) recording
  • Work Item Call - 09 Jun 2021 - (1000ET) canceled
  • Work Item Call - 16 Jun 2021 - (1000ET) rescheduled to 18 Jun 2021 - (0800ET)
  • Work Item Call - 18 Jun 2021 - (0800ET) recording
  • Work Item Call - 23 Jun 2021 - (1000ET) recording
  • Work Item Call - 30 Jun 2021 - (1000ET) canceled
  • Work Item Call - 07 Jul 2021 - (1000ET) canceled
  • Work Item Call - 14 Jul 2021 - (1000ET) recording
  • Work Item Call - 21 Jul 2021 - (1000ET) canceled
  • Work Item Call - 28 Jul 2021 - (1000ET) canceled
  • Work Item Call - 04 Aug 2021 - (1000ET) summer break
  • Work Item Call - 11 Aug 2021 - (1000ET) summer break
  • Work Item Call - 18 Aug 2021 - (1000ET) summer break
  • Work Item Call - 25 Aug 2021 - (1000ET) summer break
  • Work Item Call - 01 Sep 2021 - (1000ET) recording
  • Work Item Call - 08 Sep 2021 - (1000ET) canceled
  • Work Item Call - 15 Sep 2021 - (1000ET) canceled
  • Work Item Call - 22 Sep 2021 - (1000ET) recording
  • Work Item Call - 29 Sep 2021 - (1000ET) recording
  • Work Item Call - 06 Oct 2021 - (1000ET) canceled
  • Work Item Call - 13 Oct 2021 - (1000ET) canceled
  • Work Item Call - 20 Oct 2021 - (1000ET) canceled
  • Work Item Call - 27 Oct 2021 - (1000ET) recording
  • Work Item Call - 03 Nov 2021 - (1000ET) recording
  • Work Item Call - 10 Nov 2021 - (1000ET) canceled
  • Work Item Call - 17 Nov 2021 - (1030ET) recording
  • Work Item Call - 24 Nov 2021 - (1000ET) canceled
  • Work Item Call - 01 Dec 2021 - (1000ET) canceled
  • Work Item Call - 08 Dec 2021 - (1000ET) recording
  • Work Item Call - 15 Dec 2021 - (1000ET) winter break
  • Work Item Call - 22 Dec 2021 - (1000ET) winter break
  • Work Item Call - 29 Dec 2021 - (1000ET) winter break
  • Work Item Call - 05 Jan 2022 - (1000ET) winter break
  • Work Item Call - 12 Jan 2022 - (1000ET) canceled
  • Work Item Call - 19 Jan 2022 - (1000ET) canceled
  • Work Item Call - 26 Jan 2022 - (1000ET) recording
  • Work Item Call - 02 Feb 2022 - (1000ET) canceled
  • Work Item Call - 09 Feb 2022 - (1100CET) recording
  • Work Item Call - 16 Feb 2022 - (1100CET) recording
  • Work Item Call - 23 Feb 2022 - (1100CET) canceled
  • Work Item Call - 02 Mar 2022 - (1100CET) canceled
  • Work Item Call - 09 Mar 2022 - (1100CET) canceled
  • Work Item Call - 16 Mar 2022 - (1100CET) recording
  • Work Item Call - 23 Mar 2022 - (1100CET) canceled
  • Work Item Call - 30 Mar 2022 - (1100CET) canceled
  • Work Item Call - 06 Apr 2022 - (1100CET) recording
  • Work Item Call - 13 Apr 2022 - (1100CET) recording
  • Work Item Call - 20 Apr 2022 - (1100CET) recording
  • Work Item Call - 27 Apr 2022 - (1100CET) canceled (due to IIW)
  • Work Item Call - 04 May 2022 - (1100CET) canceled
  • Work Item Call - 11 May 2022 - (1100CET) canceled
  • Work Item Call - 18 May 2022 - (1100CET) canceled
  • Work Item Call - 25 May 2022 - (1100CET)
  • ...

Meeting - 20 December 2021 - (1400 ET) canceled

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Short updates regarding Universal Resolver
  5. Continued discussion of did:keri
    • Witnesses and resolution
  6. Other topics?

Attendees

Meeting - 06 December 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
    • Christoph (OwnYourData)
    • Wolfgang Kampichler (OwnYourData)
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Vacation schedule?
  5. Continued discussion of did:keri and relation to other DID methods
    • Work item: Type of identifiers this method supports and their intended use-cases (e.g., did:key)
    • Other work items: How to incept KERI-based DIDs and DID Documents with multiple keys associated with them
    • How to use events and how to use the KERI structure
    • Independent KERI key rotation
    • KERI and did:peer - efforts to align
    • Q: Open topic: How does the method prove uniquness?
    • KERI is described in a whitepaper. Goal: to summarise the core concepts and processing rules
    • https://github.com/decentralized-identity/keri/tree/master/kids
    • Q: Implementation maturity?
      • Implementation by Jolocom (in Rust) - implements the core
      • Other implementations - GO, Javascript
    • Q: KERI resolution
      • Multiple witnesses
      • Direct/indirect approach
      • Open question: how witnesses are defined? (public keys)
  6. did:oyd method introduction: content-based addressing, does not rely on a blockchain, using event log for updates

Attendees

  • Eugeniu Rusu
  • Alen Horvat
  • Juan Caballero
  • Christoph Fabianek
  • Wolfgang Kampichler
  • David Waite
  • Joachim
  • Tom Jones

Meeting - 22 November 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. [Jolocom team] Current status of did:keri, and adding it as a work item to the ID WG.
    • Information and contextual documents: https://hackmd.io/@RYgJMHAGSlaLMaQzwYjvsQ/ByAYibtdF
    • Current did:keri method specification: https://identity.foundation/keri/did_methods/
    • Quick intro to KERI
      • KERI defines a number of events (e.g. inception, rotation, delegated inception, etc.), and also data structures and rules for processing them. Processing events leads to the current state of the identifier.
      • There are different types of identifiers, and different ways how events can get exchanged, e.g. ephemeral mode, exchange with counterparty (direct mode), exchange via witnesses (indirect mode).
      • The controller can select what witnesses they like, witnesses can also be rotated. This adds an abstraction layer, witnesses can be anything (ledger, or personal server, etc.)
    • Current status of did:keri
      • Previously there was did:un, some features were not yet supported. Jolocom had an implementation of direct mode, the intention was to use it on mobile wallets.
      • Then the intention was to switch from did:un to a more robust implementation of did:keri, using some good learnings from the initial experimentation work.
      • Some work is split across different environments, so besides a documentation effort there also needs to be some alignment.
      • The goal is to continue and further expand the work on the DID method specification, to figure out how all the KERI building blocks can be utilized together in a method spec.
      • In the future, the roadmap also includes globally resolvable (anywise) identifiers.
      • Some questions are still open, e.g.: How is a did:keri globally resolvable? How do I know what are the witnesses? How exactly do you contact the witness? How are different key purposes mapped to a key event log? How can additional metadata be associated with a DID? How do you implement discoverability?
      • Does did:keri by itself make sense, or only "KERI in the context of an existing DID method" (e.g. did:indy:keri)?
    • Next steps
      • The work in the KERI WG is in a special state. The goal is to "wrap" that current status of KERI so that the KERI spec work goes into a "sleep" state. There are two communities, one working in the Trust-over-IP Foundation (ToIP), one working at DIF.
      • The proposal is to contribute the KERI work itself to the Applied Cryptography Working Group, and the did:keri work to the Identifiers & Discovery Working Group (this group).
  5. Other topics?

Attendees

  • Markus Sabadello
  • Eugeniu Rusu | Jolocom
  • Alen Horvat
  • Juan Caballero
  • Brian Richter
  • Christoph Fabianek
  • David Waite
  • Ezequiel
  • joachim
  • Stephen Curran

Meeting - 08 November 2021 - (1400 ET) canceled

Meeting - 25 October 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Check status of work items: https://github.com/decentralized-identity/identifiers-discovery/issues
  5. Check status of work item calls: https://github.com/decentralized-identity/identifiers-discovery/blob/main/agenda.md#special-work-item-calls
  6. Discuss next goals/milestones of the I&D WG.
  7. Other topics?

Attendees

  • Markus Sabadello
  • Alen Horvat
  • Kaliya
  • Tom Jones
  • Charles Lehner

Meeting - 11 October 2021 - (1400 ET) canceled

Meeting - 27 September 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. US mobile driver's license comment period: https://www.regulations.gov/commenton/DHS-2020-0028-0001
    • Discussion on RealID and ISO 18013-5: https://www.iso.org/standard/69084.html
    • Introduction to mDL technology
      • Hashes of each data element, bundle is signed
      • Age over X, selective disclosure is "clunky" but supported
      • No trust in user hardware, all calculation is done by issuer
    • Discussion on difference between ISO mDL and W3C VC standards
      • Competition or coexistence? Both have some support.
      • mDL written by issuers for issuers, more work needed on user and verifier perspectives.
      • mDL is not decentralized.
    • Digital wallets in Europe vs US
      • Who will isse the wallets? Centrally by the state, or free market with certification?

Attendees

  • Markus Sabadello
  • Alen Horvat
  • Chris Kelly
  • Andrew Hughes
  • Tom Jones
  • Kaliya Identity Woman

Meeting - 13 September 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Change call schedule to bi-weekly?
  5. [Liam McCarty, Unum ID] Bridging Digital and Physical: Make Identifiers Identify
    • Summary:
    • Identifiers are only useful if they identify, which requires them to be reliably associated with people and things. In this talk, Liam McCarty of Unum ID will explain how to make such associations by leveraging the modern infrastructure of secure hardware and device biometrics. But he will also show that there’s currently a wide gap between how available this infrastructure is to different types of applications, and he will argue that this has been a significant barrier to adoption of decentralized identity systems. Finally, he will outline a path toward closing the gap and stress the importance of public advocacy in achieving that goal, which will finally make possible identifiers that identify.
    • Notes:
    • Association between physical world and digital identity is important.
    • In the physical world, we have "built-in private keys", we "are" a wallet.
    • There is a difference between access to hardware crypto on mobile vs. web.
    • Wallets in browsers are really hard, e.g. Safari deletes everything ter 1 week.
    • There is a need for generic hardware backed cryptographic signatures on the web.
    • Standards exist, but are of limited use:
    • Calling for community action to support this, e.g. see these issues:
    • Some abandoned work on hardware based secure services:
    • Call to Action:
    • We need community action to advocate for general, hardware backed cryptographic signatures on the web! This would make it possible to build decentralized identity wallet web apps, not just mobile ones, dramatically improving odds of adoption. Please help the cause by commenting on the WebAuthn and WebCrypto GitHub issues pages, supporting my proposals there, and generally increasing awareness around this topic. This is a technical change that requires a decidedly nontechnical solution: community advocacy. Thanks for your help!

Attendees

  • Markus Sabadello
  • Alen Horvat
  • Liam McCarty
  • Chris Kelly
  • Charles E. Lehner
  • Tom Jones

Meeting - 06 September 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Discussion in Slack: If you receive a message from a DID, what are approaches to information discovery on that DID?

Attendees

  • Chris Kelly
  • Cristopher Fabianek
  • Tom Jones
  • Alen Horvat

Meeting - 30 August 2021 - (1400 ET) summer break

Meeting - 23 August 2021 - (1400 ET) summer break

Meeting - 16 August 2021 - (1400 ET) summer break

Meeting - 09 August 2021 - (1400 ET) summer break

Meeting - 02 August 2021 - (1400 ET) summer break

Meeting - 26 July 2021 - (1400 ET)

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Update on Work Items
  5. Continue discussion on historical key resolution?

Attendees

Meeting - 19 July 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Discuss ID WG call schedule
    • Proposal to move Universal Resolver Work Item Call to 0800ET instead of 1300ET.
    • Proposal to suspend main ID WG calls during August.
  5. Short discussion around Solid and DIDs.
  6. Universal Resolver returning a key in a given format (e.g., JWK(S))
    • Discussions on transform-keys DID URL parameter.
    • Specification is incomplete and needs more work. PoC has been implemented in Universal Resolver.
    • Parameter is registered in DID Spec Registries (which is a "note", not a "standard").
    • Discussion on trust boundaries and security implications of transforming keys in a DID document (only public keys!)
    • What are possible values? JWK, JWKS, base58, multibase, PEM, ...?
    • Discussion on this approach vs. use media types as in https://did.key.transmute.industries/.
  7. Continue work on historical key resolution
  8. Other topics?

Attendees

  • Markus Sabadello
  • Alen Horvat
  • Tom Jones
  • Daniel Buchner

Meeting - 12 July 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. [Daniel] Historical key resolution
    • A DID document could point to a hub, which contains a list of historical keys associated with the DID. This list is signed by a current DID controller key.
    • Using DID URLs, it should be possible to point to a specific historical key at a specific point in time, and it can be dereferences publicly by anyone.
    • Maybe similar to this: did:example:123?service=IdentityHub&relativeRef=/CollectionsQuery?uri=https://identity.foundatio/KeyHistory#key-32
    • See https://identity.foundation/identity-hub/spec/#did-relative-urls
    • Discussion around how can this be trusted, since it's in your identity hub and you can change it at any time, and this information is separate from the underlying DID verifiable data registry.
    • Advantage: This is method-independent.
    • Discussion on relation between this approach and KERI's Key Event Logs.
    • Discussion on implementing this in the Universal Resolver. This could be supported as an extension of the UR; individual DID method drivers don't have to do anything.
    • The ID WG could start a new work item which defines the data structure of historical keys, as well as the format of DID URls that point to them.
  5. Other topics?

Attendees

  • Markus Sabadello
  • Daniel Buchner
  • Alen
  • Juan Caballero
  • Ezequiel
  • Tom Jones
  • Bradley Hinson
  • Balázs Nemethi

Meeting - 05 July 2021 - (1400 ET) canceled

Meeting - 28 June 2021 - (1400 ET) - recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Special Work Item Calls
  5. [Alen] EBSI Ledger and Trust
    • European Blockchain Service Infrastructure
    • List of Trusted Registries
    • Registry Properties
    • Discussion about "Onboarding Service"
    • Discussion LoA, key security, eIDAS
    • Current Status of EBSI
  6. Other topics?

Attendees

  • Markus Sabadello
  • Alen Horvat
  • Christoph (OYD)
  • Juan Caballero (DIF)
  • Kaliya Identity Woman
  • Nikos Fotiou
  • Steve Todd
  • Tom Jones

Meeting - 21 June 2021 - (1400 ET) - recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Short update on Verifiable Conditions
  5. Review of transform-keys DID parameter
    • Outdated in various ways (e.g. matrix parameters, "publicKey" property), needs to be updated to match latest DID Core
  6. Discussion on DHS request for comments on mDL:
  7. Discussion on various eID projects in US and EU
  8. Other topics?

Attendees

  • Markus Sabadello
  • Alen Horvat
  • Tom Jones
  • Juan Caballero
  • Balázs Nemethi

Meeting - 14 June 2021 - (1400 ET) canceled

Meeting - 07 June 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Special Work Item Calls
    • Markus gave a quick update from the Special Work Item Calls about DID Registration and the Universal Resolver
  5. [ezequiel] "controller" property in DID documents and verification methods.
    • "controller" on the top level seems clear, but on the "verificationMethod" is less clear.
    • "verificationMethod" can only have a single "controller", but verification methods can in fact be "controlled" by multiple entities (e.g. see the next topic - Verifiable Conditions)
    • See e.g. w3c/did#697
    • Seems like in practice we always have did_document.id === did_document.verificationMethod[N].controller
  6. [Jack] Updates from Verifiable Conditions - https://github.com/w3c-ccg/verifiable-conditions
  7. Other topics?

Attendees

  • Markus Sabadello
  • Ezequiel
  • Jack Tanner
  • Ajay Jadhav
  • Samuel Smith

Meeting - 31 May 2021 - (1400 ET) canceled

Meeting - 24 May 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Special Work Item Calls
  5. [ezequiel] "controller" property in DID documents and verification methods.
    • Ezequiel did not attend and the topic was skipped.
  6. [Samuel Gómez Escalante] DID Key rotation/revocation
  7. Other topics?

Discussion topic: DID Document signatures Samuel G.:

  • DID Document owner signs the DID Document to protect the DID Document integrity.
  • Purpose: to abstract the DID Registry implementation.
  • The proof is static.
  • The computation proof is automated.

Markus:

  • The topic has been discussed many times.
  • Outcome: DID Document signature by itself does not prove control of the DID.
  • Only DID Document signature and anchoring (in a registry) can prove the actual ownership of the DID Document.

Alen: What is the added value of having a signature?

Samuel G.:

  • DID Document integrity protection.
  • Minimizing the technology dependence (of the registries).

Markus:

  • DID Document signature only assures the DID Document integrity and not the link between the DID and DID Document. Ideally, you should run your own universal resolver and perform the full resolution.

Discussion outcomes:

  • DID Documents may or may not require a signature, depending on the registry design.
  • DID Document signature only proves the DID Document integrity.
  • Only DID Document signature and anchoring (in a registry) can prove the actual ownership of the DID.
  • Reliable DID resolution is important.

Discussion topic: DID key rotation and revocation

Open PRs

Samuel Smith clarifies the authorisation models

https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/IdentifierTheory_web.pdf

Tom points out the importance of machine-readable format for verification/validation.

Discussion outcome: Rotation/revocation topics should be addressed in the following meeting

Attendees

  • Samuel Gomez - Gataca
  • Juan Caballero
  • Markus Sabadello
  • Tom Jones
  • David Waite
  • Charles E. Lehner
  • Balázs Nemethi
  • Samuel Smith
  • Alen Horvat

Meeting - 17 May 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. New Work Item Call schedule announced (DID Registration WI, Universal Resolver WI)
  5. Universal Registrar - an overview
    • Universal Registrar - can obtaining access to registries be unified (from the wallet implementation perspective)?
      • References:
      • Issue:
        • Onboarding/getting access to a DID registry is usually DID-registry-specific.
      • Proposals:
        • Consider the most frequent flows:
          • Redirect to a webpage (authentication or other operations are performed outside the wallet)
          • Authentication via API (some existing Universal Registrar drivers support this)
        • Proposal should work for most DID methods (e.g., did:web, Sovrin, sidetree)
        • A more detailed compatibility analysis is required
      • Outcomes
        • Proposals will be further analysed and discussed in the Universal Registration call
        • Issues will be opened in the Universal Registration repository
  6. Short discussion about DID key rotation/revocation
    • DID Key rotation/revocation and trust

Attendees

  • Markus Sabadello
  • Juan (DIF/Spruce)
  • Samuel Smith
  • Balázs Némethi
  • Steve Todd
  • Tom Jones
  • Alen Horvat

Meeting - 10 May 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. New repository donations:
  5. Special Topic Calls: #1
    • Will discuss and find appropriate times via Slack/email.
  6. [Boris Mann, Brooklyn Zelenka, Jeff Griffiths] Overview of Fission proposed approach to DID resolve / discovery in signing up for an account / linking DIDs
    • Fission's entire account system is built around DIDs.
    • App publishing platform and SDK.
    • Giving every user an end-to-end encrypted data store, using IPFS heavily.
    • In the account system, people select a username in a Fission namespace (e.g. boris.fission.name). The human-readable identifier can be used to discover a DID (using https://datatracker.ietf.org/doc/draft-mayrhofer-did-dns/). A did:key is created for users. The Fission server also has a DID.
    • Are there privacy issues with using domain names as user identifiers?
    • How can the auth system accept "remote" DIDs, i.e. interoperate with other DID methods (e.g. did:ion)? The "remote" DID could then "control" the Fission-internal DID.
    • How can the auth system advertise to someone that they can enter a DID to connect to the system?
    • Considering Webfinger discovery based on email-like identifiers; want to avoid NASCAR problem.
    • OIDC SIOP work seems relevant (ongoing at OpenID Foundation).
    • IIW had a session about SIOP Chooser (see https://docs.google.com/presentation/d/1OaMecHecTUexv1skJZoYzJoHKYH8H03REFpFstLRjPg/). Tom Jones is one of the people leading this effort.
  7. Other topics?

Attendees

  • Markus Sabadello
  • Alen Horvat
  • Boris Mann
  • Ezequiel
  • Balázs Némethi
  • Brooklyn Zelenka
  • Charles E. Lehner
  • Jeff Griffiths
  • Jeremie Miller
  • Juan (DIF/Spruce)
  • Samuel Smith
  • Tom Jones

Meeting - 3 May 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Continue with organizational topics in ID WG
    • New co-chair Alen Horvat
    • Discussed regular call schedule, work items, special topic calls
  5. Discussion around persistence and versioning of JSON-LD contexts, and implications on Linked Data Signatures
  6. Discussion around data structures and other topics in the CCG's Universal Wallet 2020 specification
  7. Other topics?

Attendees

  • Markus Sabadello
  • Orie Steele (Transmute)
  • Samuel Smith
  • Alen Horvat
  • Balázs Némethi
  • Tom Jones

Meeting - 26 Apr 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Organizational topics in ID WG
    • Sam Smith will step down as co-chair
    • Alen Horvat proposed as new co-chair
    • If there are any other proposals for co-chairs, or questions/feedback from the WG, please ask in our Slack channel
    • Consider changing the schedule of future calls (e.g. bi-weekly regular calls, with Special Topic calls)
  5. Report-out from IIW
  6. Discussion around .well-known and did:web
    • Dmitri is willing to give an update on latest developments
  7. Other topics?

Attendees

  • Markus Sabadello
  • Dmitri Zagidulin
  • Juan Caballero
  • Samuel Smith
  • Alen Horvat
  • Balázs Némethi
  • Tom Jones

Meeting - 19 Apr 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. [Markus, Bernhard, Niclas] Updates to Universal Resolver/Registrar configuration, and work on Helm charts:
  5. [Philip Feairheller, Sam Smith] KERI-based DID methods, and use of DID Resolution metadata

Attendees

  • Markus Sabadello
  • Tom Jones
  • Juan Caballero
  • Balázs Némethi
  • Bernhard Fuchs
  • Niclas Mietz (Spherity)
  • Philip Feairheller
  • Samuel Smith

Meeting - 12 Apr 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Breaking changes in DID Core JSON-LD context:
    • w3c/did-extensions#277
    • Strictly speaking, all UR DID method implementations are now broken.
    • Discussion around changing JSON-LD contexts, caching, versioning, hashlinks
    • UR could implement a "fixing layer" for a transitional period, and simultaneously try to motivate implementers to fix their drivers.
  5. Universal Resolver policy questions about driver submission and maintenance
    • decentralized-identity/universal-resolver#186
    • UR currently supports several DID methods that are not in the DID spec registries.
    • Probably we should have stricter policies going forward (e.g. only accept drivers for DID methods in the W3C method registry)
    • We will work on a proposal and present to the group.
  6. Other topics?

Attendees

  • Markus Sabadello
  • Samuel Smith
  • Bernhard Fuchs
  • Charles E. Lehner
  • David Waite
  • Juan (DIF)
  • Philip Feairheller
  • Tom Jones

Meeting - 05 Apr 2021 - (1400 ET) canceled

(Canceled due to Easter holidays)

Meeting - 29 Mar 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Review DID WG test suite: https://github.com/w3c/did-test-suite/
    • The repo has issues for each part of the DID Core spec. Some PRs exist already to implement the tests.
    • Overall structure of test suite will probably still change (location of input files, re-use of test code, etc.)
    • Discussion if implementers will simply submit their result data, or if the test suite will have a "dynamic" execution component that automatically tests implementations.
  5. Other news from W3C DID WG.
  6. Other topics?

Attendees

  • Markus Sabadello
  • Juan Caballero
  • Tom Jones
  • Charles E. Lehner
  • Balázs Némethi

Meeting - 22 Mar 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. [JackT] Updates on "VerifiableCondition"
  5. Other topics?

Attendees

  • Markus Sabadello
  • Jack Tanner
  • Caspar Roelofs (Gimly)
  • Charles E. Lehner
  • Daniel McGrogan
  • Jeremie Miller
  • Tomj

Meeting - 15 Mar 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions

  2. ID WG participation tracking

  3. Agenda creation/review/prioritization

  4. [DanielK, JonC] New DID method on the Solana blockchain

    • did:solid, but not related to Solid (Social Linked Data) project
    • Solana blockchain is cheap and fast (1000s of transactions per dollar, but data storage is not as cheap). There is "rent", which can be decreased but never increased.
    • Version 0.1, will still be changed/optimized
    • Simple CRUD approach to put DIDs on blockchain. Solana has the concept of an "account", that's what you pay rent for. It will serialize a document and store the byte array on chain.
    • Daniel+Jon have worked on a driver for both the Universal Resolver and Universal Registrar. An instance of the Universal Resolver is running at:
    • https://did.civic.com/
    • Some discussion around design of Universal Registrar, e.g. what are the inputs, who pays for the transactions, etc.
    • [CharlesEL] Spruce Systems has also worked on a DID method based on Solana, perhaps there is potential to collaborate.
    • Links:

  5. Other topics?

Attendees

  • Markus Sabadello
  • Daniel Kelleher
  • Charles E. Lehner
  • Jeremie Miller
  • Jon Cinque
  • Samuel Smith
  • Tom Jones
  • Orie Steele

Meeting - 08 Mar 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. [Jack] Continue discussion on multisig and delegation in DID methods:

Attendees

  • Markus Sabadello
  • Caspar Roelofs
  • Charles E. Lehner
  • David Waite
  • Jeremie Miller
  • Joel Thorstensson
  • Juan Caballero
  • Samuel Smith
  • Tom Jones

Meeting - 01 Mar 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Controller, verification methods, authorization in DID Core
  5. [Jack] Support for multisig and delegation in EOSIO
    • Presentation by Jack about EOS chain and larger EOSIO ecosystem
    • EOS has an "account" concept as an abstraction layer; the account identifier is not derived from a key
    • Detailed discussions about multi-sig verification methods and delegation methods
    • There is a difference between 1. making a DID method that internally uses these features, and 2. exposing this in a DID document in a method-independent way. On the call, there was consensus that the latter would be highly desirable.
    • Consensus that a new cryptosuite should be defined (as a work item in W3C CCG or DIF)
    • If possible, the blockchainAccountId property should be re-used.
  6. Related topics in other DID methods
    • Besides EOS, this is also relevant to did:indy, Ripple, and KERI-based DID methods

Attendees

  • Markus Sabadello
  • Jack Tanner
  • Orie Steele
  • Caspar Roelofs
  • Jeremie Miller
  • Juan Caballero
  • Michael Herman
  • Samuel Smith
  • Tom Jones

Meeting - 22 Feb 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Updates on progress on DID Core in W3C DID WG

Attendees

  • Markus Sabadello
  • Samuel Smith
  • Charles E. Lehner
  • Dmitri Zagidulin
  • Jack Tanner
  • Juan Caballero
  • Tom Jones

Meeting - 15 Feb 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Dillo plugin for DID URLs
    • Can resolve DIDs inside a browser, using a local instance of DIDkit
    • Can use Universal Resolver as a fallback
    • Built-in DID resolution in browser is preferable to remote resolver service
  5. Updates on Universal Resolver/Registrar
    • Working on a DIDComm interface for the Universal Resolver
    • Alternative to using HTTP interface
    • Chicken-and-egg problem (you first need to resolve DIDs to do DIDComm)
  6. Discussion on human-readable names and DIDs
  7. Discussion on use of multiple keys for controlling a DID
    • How can you express in a DID document that you want to use multiple keys to authenticate? Define a verification method that consists of multiple other verification methods?

Attendees

  • Markus Sabadello
  • Jack Tanner
  • Juan Caballero
  • Kaliya Identity Woman
  • Samuel Smith
  • Tom Jones
  • Charles E. Lehner
  • Oliver Terbu

Meeting - 08 Feb 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. News on Fuzzy Encryption:
    • Finished work on a C++ implementation
    • Build script that generates WASM, can be consumed by JS
    • When not in native C++ form, it needs a wrapper for input of random bytes
    • Library can encrypt secrets, can decrypt with different inputs; technically different from Shamir, but has similar properties
    • The encrypted secret can be a symmetric key seed
  5. News on KERI:
    • KERI is about to become its own Working Group, charter has been approved
  6. Guidance on specifying a new DID method
    • Interest in creating a new DID method for eos.io
    • eos.io has existing concepts of "accounts" that could be used as a basis for DIDs
    • How to write a DID method specification? (needs to define DID syntax, DID operations, Privacy&Security Considerations)
    • DID method can be registered in DID Spec Registries
    • Driver implementation can be submitted to the Universal Resolver
    • Discussion around creating new DID methods and differences between methods
    • Discussion around new DID methods that incorporate KERI principles

Attendees

  • Markus Sabadello
  • Alen Horvat
  • Daniel Buchner
  • Michael Herman
  • Adi (Entrustient)
  • Caspar Roelofs
  • Charles E. Lehner
  • Jack Tanner
  • Jeremie Miller
  • Juan Caballero
  • Rouven Heck
  • Samuel Smith
  • Tom Jones
  • Kaliya Identity Woman

Meeting - 01 Feb 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Continue discussion on DID CRUD operations, including architectures, interfaces, implementations (such as Universal Resolver/Registrar, ACA-py, aries-framework-go, Veramo, DIDKit)
    • Introduction to DIDKit:
      • Support for Verifiable Credentials, LD Proofs, JSON-LD normalization, VC HTTP API, and more.
      • Support for multiple DID methods in core, library can be extended with additional DID methods by implementing the same Rust trait.
      • Rust traits match functionality in DID Core and DID Resolution.
      • Support for did:doge (identical to did:btcr with better privacy characteristics)
    • Discussion on architectures of DID registration software
      • Security and trust issues if a hosted service is involved in DID write operations.
      • User/client should not sign something they don't understand.
      • Startups create new DID methods all the time, how can they all be supported?
    • Discussion around government-approved cryptography, and adoption of DIDs.
  5. Consider proof-of-control
    • Sam: We don't need DID documents, we only need to establish control authority, and then issue verifiable credentials.

Attendees

  • Markus Sabadello
  • Alen Horvat
  • Balázs Nemethi
  • Charles Cunningham
  • Charles E. Lehner
  • Ian Yu
  • Juan Caballero
  • Martin Riedel
  • Rouven Heck
  • Samuel Smith
  • Tom Jones
  • Wayne Chang

Meeting - 25 Jan 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Integration between ACA-py/Veramo/aries-framework-go and Universal Resolver.
    • DID write operations in aries-framework-go:
      • Supports did:web, did:key, did:peer, you can inject additional DID method support
      • Ability to configure Universal Resolver
      • For DID updates, you can pass in DID documents for doing updates (patches can be automatically constructed from the diff)
      • Using WebKMS ("KeyRetriever" interface) for write operations
    • DID write operations in Veramo:
      • Veramo acts as a store that links DIDs to their keys
      • DID that needs to be updated need some crypto operations with those keys
      • We tried to come up with an abstraction layer, including add and remove operations for keys and services
    • DID write operations in Universal Registrar:
      • https://uniregistrar.io/
      • Set of Docker images similar to Universal Resolver
      • Private keys are generated by the individual drivers and then returned to a client <-- bad security!!
      • API has state ("finished", "error", "action", "wait") and sometimes requires multiple steps
    • Discussion around "trusted endpoints" for DID methods
      • To add support for resolving a DID method, you could run a driver locally as part of the resolver, or configure a trusted remote endpoint
      • This can help minimize the amount of code that has be implemented

Attendees

  • Troy Ronda
  • Ajay Jadhav
  • Alen Horvat
  • Andrei Mikhin
  • Artur Philipp
  • Charles Cunningham
  • Dmitri Zagidulin
  • Juan Caballero
  • Lionel LONKAP
  • Samuel Smith
  • Steve Todd
  • Tom Jones
  • Tomislav Markovski

Meeting - 18 Jan 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Preparation for DIF F2F - https://docs.google.com/spreadsheets/d/1hVnwrnU7QOp_rA7AcK2NTQkflSAg0zvQ3-We2DqyRpk/
  5. Review of current work items
    • Discussed state of did:peer with regard to recent developments in DIDComm v2 and KERI
    • KERI implementations are moving ahead in multiple programming languages.
    • Thanks @tmarkovski for new contribution of did:key implementation in Rust! https://github.com/decentralized-identity/did-key.rs
  6. Use of colons in DID syntax
    • E.g. in did:ethr:testnet:1235426534, you have a colon as part of the method-specific identifier. Does this mean you have to know about all DID methods in order to be able to parse DIDs?
    • See reviews by W3C TAG about DID Core spec: w3ctag/design-reviews#556

Attendees

  • Markus Sabadello
  • Samuel Smith
  • Tom Jones
  • Balázs Nemethi
  • Juan Caballero
  • Tomislav Markovski

Meeting - 11 Jan 2021 - (1400 ET) canceled

Meeting - 04 Jan 2021 - (1400 ET) recording

Agenda

  1. Welcome and introductions
  2. ID WG participation tracking
  3. Agenda creation/review/prioritization
  4. Upcoming DIF F2F - https://docs.google.com/spreadsheets/d/1hVnwrnU7QOp_rA7AcK2NTQkflSAg0zvQ3-We2DqyRpk/
    • Since the ID WG has many work items, we should do a high-level overview of everything in our "main" 15 min session, then have 15 min breakout sessions for the work items people care about
  5. Plans for 2021
  6. Wallet certification
    • Short discussion on how wallets get certified and which organization(s) would do this.
    • Could be part of Governance Frameworks developed by Trust-over-IP foundation.

Attendees

  • Markus Sabadello
  • Juan Caballero
  • Balázs Nemethi
  • Charles Cunningham
  • Samuel Smith
  • Maarten (Sphereon)
  • Tom Jones