/
2021-09-13 ACDC Meeting Notes

2021-09-13 ACDC Meeting Notes

Owned by Kevin Griffin
May 09, 2023

Brief update on wiki page reorg—Drummond Reed

  • Meeting page has been broken out into a standalone page (this one)
  • A table of deliverables has been added to the ACDC home page
    • We should be sure this table is complete and kept current

IIW Strategy:  Daniel Hardman

  • Daniel: How many sessions would we like at IIW?
  • Sam: one session per day
  • Daniel: in previous IIWs, Sam had done 2-3 sessions per day
  • Sam: plan on one per day, and then possibly have a second one
  • Robert: have one technical session, and one non-technical session focused on use cases and business cases
    • Data flows, data supply chain, product supply chain
    • For example, GS1 has very specific requirements that the KERI family of specs can meet
  • Daniel: can we develop a spreadsheet showing a classic product comparison table (similar to what the DIF DIDComm WG has created for DIDComm & HTTP(S))
    • Robert liked the idea of the table being something that stresses the business
    • ACTION: Robert Mitwicki will prepare a draft of a feature comparison table before our next meeting.
    • ACTION: Drummond Reed to talk to Brent Zundel about a session about VC V2 at IIW
  • Proposed sessions
    • GLEIF: Distributed Multi-Sig Chained Credentials using KERI and ACDC — Philip Feairheller and Kevin Griffin
    • What is ACDC? — Sam Smith
      • KERI and ACDC Technical Session
      • Covers all the contributing specs
    • Why ACDC? (And Why Not _____?) — Robert Mitwicki
      • This would include A Feature Comparison Table
    • Secure Attribution with KERI: How it Fixes the Broken Internet — Sam Smith
    • Practical Introduction to KERI: How Can I Actually Use it Today? - 

ACDC Specification Strategy:  Daniel Hardman

  • SAID spec—Sam Smith
  • IXP spec—Phil Feairheller
  • PXP spec—Phil Feairheller
  • PTel spec—Phil Feairheller
  • CESR spec—Sam Smith
  • CESR proof spec—Phil Feairheller
  • AID spec—Sam Smith
  • ACDC spec—Sam Smith
  • SIS spec—Robert Mitwiki
  • ACTION: Drummond Reed to update the ACDC home page deliverable table with these leads

General Discussion:

  • Suggestion is that KERI is too large to be a single spec, so break it into smaller specs.
  • For example, CESR can be broken out into a separate composable serialization spec.
  • And you separate out identifier specs.
  • Once you take the identifier formats and composable streaming format out, then KERI becomes a definition of events.
  • We also talked about the future of the W3C Verifiable Credentials spec—Brent Zundel is working on the charter for the V2 Working Group
    • What is being discussed is the possibility of the new WG taking a "Big Tent" approach
    • In that case, ACDC would be one of the "branches" or "options" or "families" of a W3C VC V2 compliant
    • The big question is whether others that would be in that big tent would be tolerant (or even welcoming) of having the ACDC family under the tent
  • Sam brought up the question of how KERI and ACDC deal with dynamic data
    • DIDs and DID documents try to be dynamic and VCs try to be dynamic, but neither does it with strong security
    • KERI and ACDC have a way of handling dynamic data with a zero-trust security model
    • Robert talked about how KELs can essentially act as microledgers ("single node blockchains") to trace the changes in state to any kind of data set
    • Sam agreed to you need both authentity, monotinicity, and protection from replay event logs
      • DID docs use the CRUD model
      • This requires using the RUN model (Read, Update, Nullify)
  • ACTION: Drummond Reed to ask Elisa to change the ACDC meeting to auto-record