Zoom Meeting Link / Recording
Attendees
Sam Smith Kevin Griffin Philip Feairheller Henk van Cann Ed Eykholt @Rubel Charles Lanahan @Daniel Lenksjö Lance Byrd Kent Bull Daniel Hardman Fergal O'Connor Petteri Stenius Steven Milstein Nuttawut Kongsuwan
Agenda Items and Notes (including all relevant links)
| Time | Agenda Item | Lead | Notes |
| 5 min | - Start recording
- Welcome & antitrust notice
- Introduction of new members
- Agenda review
| Chairs | - 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:
|
| 5 mins | Review of action items from previous meeting | Chairs | - Future discussion show the dependencies among the specs and mini specs.
- Future discussion about first steps in doing a CESR/KERI/ACDC implementation
|
| 5 mins | Announcements | TF Leads | News or events of interest to members: - DICE un-conference. Jun 18th - 20th 2024 in Zurich
|
| 5 mins | Reports | Open | - Specifications
- Issues sorted by Kevin and Sam
- Biggest outstanding chunk is fixing up all the references
- KERIpy
- Release candidate ready to merge
- KERIA
- Release candidate ready to merge
- Signify-TS
- Release candidate ready to merge
- Signifypy
- Release candidate ready to merge
- did:webs
- Upgraded reference implementation to 1.1.0 KERIpy
- Designated alias credential issue - perhaps one-of issue.
|
| 25 mins | Discussion | Open | - https://github.com/trustoverip/tswg-cesr-specification/issues/53
- Updated issue with suggested fix
- Multiple implementations and interoperability Kevin Griffin
- ToIP currently considering a requirement to have at least 2 implementation of the specifications that can demonstrate interoperability.
- CESR is likely covered with Signify-TS (CESR-TS) and CERSide and KERIpy.
- ACDC could be solved if we can issue a credential from KERIpy and perhaps the QuIdentity's implementation (or others).
- KERIpy Interoperability Profile:
- Call for thoughts.
- For CESR, test vectors of Primitive Value, Text CESR, Binary CESR would be helpful - Not unit tests.
- For KERI, test vectors of KEL → Key State could be helpful. A KEL for each feature of KERI, Delegation, Multisig, Rotation, Interactions, etc.
- For ACDC: All outcomes of the IPEX state machine compared against a CESR stream for all the paths of the state machine.
- Merging in releases in KERIpy, KERIA, Signify-TS and Signifypy
- Two Thumbs up from Daniel Hardman
- Philip Feairheller to cut next releases of KERIpy, KERIA, SigPy and SigTS
- After release, we will attempt to upgrade development branch to Python 3.12.
- Daniel Hardman has had some problems upgrading - we will keep an eye out.
- Ruth Choueka Wallet migration question.
- Migrating a multisig AID from a command line wallet backed to a KERIA backed AID.
- We have sample script for performing the KEL migration but not TELs and Credentials
- Rubel : https://github.com/WebOfTrust/keripy/issues/672
- How do we allow an issuer to declare / decide that credential issuances should be public (is it per registry?)
- Sam Smith - Nothing in the TEL can declare whether credentials are public, it is up to the issuer how the make these available.
- So we are looking at an implementation at the Witness level that allows Issuers to declare what credential issuances can be "scanned" publicly.
|
| 5 mins | Any other business | Open |
|
| 5 mins | - Review decisions/action items
- Planning for next meeting
| Chairs | |