Versions Compared

Key

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

Meeting Link / Recording

Attendees

...

Attendees

Drummond Reed 

Sam Smith 

Kevin Griffin 

Nuttawut Kongsuwan 

Alex Andrei 

Charles Lanahan 

Lance Byrd 

Agenda Items and Notes (including all relevant links)

  •  Lance Byrd will start an ACDC PR to the spec that describes signing
    •  Lance Byrd will provide an outline of how to use a TEL to verify the signature document
  •  Daniel Hardman will donate his dh1128 repo if ToIP will allow.... all commits are signed
TimeAgenda ItemLeadNotes
5 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
5 minsReview of action items from previous meetingChairs
  •  
Stephen Curran is pursuing a Hyperledger Labs repo for the resolver reference implementation
  • Kevin Griffin updated the wiki spaces, etc.
  •  Markus Sabadello reorganized sections and updated the references to .kel, to instead refer to the KERI Event Stream (.keri)
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
25 minsDiscussionOpen
  • Markus Sabadello architecture diagrams revisited.
    • We saw last week that reference implementations could support multiple types of resources to get the keri verification information.
      • Perhaps in the spec we consider them did.keri resources (files, oobis, watchers, db/cache, or other ways of getting a CESR stream). You could think of it as an application/cesr.keri media/mime-type that gives a CESR stream that could feed you CESR containing any mix of CBOR, JSON, etc.
      • CESR MIME type (CESR stream, not document type) is on the IANA roadmap.... so .keri extension could be misleading, what about .cesr extension? The KERI event stream that Markus Sabadello talks about in his spec is a CESR stream. This also aligns better with the Trust Spanning Protocol which will be expressed as CESR primitives. CESR is an all encompassing MIME type for KERI ACDC TSP protocol resources.
    • Prompted two new terms for the spec:
      • KERI resource (replaces .kel and .oobi terms)
        • CESR resource/mime-type/media-type
5 minsAny other businessOpen


5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs
    •  Sam Smith will pursue the IANA CESR MIME type registration within the ACDC TF
      •  Provisional registration is short-term
      •  Then work towards official registration
    •  Drummond Reed will send updated Task Force information
    •  Kevin Griffin is following up with ToIP Michelle Janata and Drummond Reed will be included.
    •  We will appoint additional chairs (currently only Phil is listed) and maintainers
    •  
    •  Stephen Curran is pursuing a Hyperledger Labs repo for the resolver reference implementation
      •  
Lance Byrd Create a PR for the spec that abstracts the verification information to CESR resources/mime type (not files) to support multiple reference implementations. The resolver can use local file(s), OOBIs, Watcher pools, DB/cache, etc for verification as long as it results in secure KEL/TEL verification.