Versions Compared

Old Version 4

changes.mady.by.user Alex Tweeddale

Saved on

compared with

New Version 5

changes.mady.by.user Alex Tweeddale

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Attendees

Agenda Items and Notes (including all relevant links)

Time

Agenda Item

Lead

Notes

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:

15 min

Intro to Task Force

Leads

  • Tim: What do we mean by a Verifiable Identifier? I.e. is a social security number a Verifiable Identifier?

    • The High Assurance DNS records with DIDs is one part, but we need to make sure the entire concept is defined before we jump into the spec

  • Scott: We need to define “verifiable” and “identifier” separately. Social security numbers do not do the validation required to tie/bind the trustworthiness of an individual

  • Alex: We should be targetted on specific identifier types, such as X.509 and DIDs rather than every possible type of identifier

  • Tim: What’s different from the DHS work?

    • Broadened to other DID methods (DHS focussed on did:web)

  • Mathieu: Should we keep focus on did:web?

  • Tim: Technological verifiability vs management verifiability - DHS method did not want to the methods for creating domain names / management

  • https://docs.google.com/presentation/d/1u6GK7oWw-ewB3lONncI1CfcMpiJ2zUT8LrUGRLuV1w8/edit

  • Tim: You do not need a web server to verify a DNS record

    • Jesse: New part of the DID core spec

    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.

    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

    • Review decisions/action items

    • Planning for next meeting 

    Leads

     

    ...