Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Meeting Link / Recording

Attendees

This is a future meeting

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
5 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
5 minsReview of action items from previous meetingChairs
5 minsAnnouncementsTF Leads

News or events of interest to members:

  • ToIP has approved the Open Web Foundation (OWF) IPR license
    • We are 15 days into the 60 day period
  • This is an OFFICIAL TF as of Thursday night
    • From the TSWG:
      • ACTION: Drummond Reed to send an email to the TSWG mailing list notifying all TSWG members of a 7 day review period for the proposed DID WebS Method Task Force, followed by a 7-day email vote seeing if there are any objections.
      • ACTION: did:webs Task Force leads to contact Michelle Janata to add their Friday meeting onto ToIP calendar once the Task Force is officially approved
      • Chairs
        • Should be listed on the wiki page. 
      • Maintainers
        • Let Kevin know
  • IIW October 2023
    • We aim to be registered did method and have an implementation in the Universal resolver
    • Note: there will also be a TSP for Muggles session at IIW, based on the recent blog post.
  • did:plc and Dimiti's did:web 2.0 (next gen) proposals discussion.
5 mins

Reports

Open
  • Upcoming milestones
  • DIF identifiers discovery "lifecycle of did:web identifiers"
  • did:webplus meeting:
    • Alex Colgan, Lance Byrd, Ben Taylor, Victor Dobs, Alex Andrei, Dimitry Zagidulin, Stephen Curran, Benjamin Goering, Juan Caballero, Markus Sabadello, Michael Lodder
    • Signed did documents:
      • Private key control = modern equivalent of ftp
      • In did:webs, what is relevant is discovery. Control is bound to the AID.
        • With all three approaches, the domain name is still difficult
    • Scalability
      • Did documents fork and must be merged back, how do you reconcile these differences over 
        • Athlete working with multiple companies, and some created things overlap, images/likeness etc. and then occasionally merge back. The core data can be highly protected (athlete in their underwear)
        • Zero-knowledge proofs.
    • On a web server, paths are secured with signatures tied to the KEL
    • Whois folder about the subject, for discovery of more information.
    • Backwards hash links vs versionId
    • did:webplus considers duplicity detection as optional
    • The feeling is that KERI is more complex than necessary to be secure
      • building UX is very hard if you don't understand the technology
    • Adoption vector of did ecosystem to vLEI/KERI ecosystem is why we need to create this bridge
      • Expand to multiple implementations, multiple credential formats, etc
    • Can we compare and can we combine LedgerDomain/ToIP and possibly combine efforts for did:webplus and did:webs
      • Find the synergies
        • Compatible syntax, one domain name works for multiple methods
25 minsDiscussionOpen
5 minsAny other businessOpen


5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs


  • No labels