Zoom Meeting Link / Recording
Attendees
Phil Feairheller Samuel Smith Kevin Griffin Ed Eykholt Joseph Hunsaker Ruth Choueka Lance Byrd Charles Lanahan Rodolfo Miranda Kent Bull @Fergal O'Connor Michael Palage Rubel Petteri Stenius Trent Larson
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 | - CESR provisional registration with IANA is complete.
|
| 5 mins | Announcements | TF Leads | News or events of interest to members: - Release Candidates of KERIpy, KERIA, SigPy, SigTS cut and waiting for feedback
|
| 5 mins | Reports | Open | - Specification Work
- Making good progress, been reviewing and merging PRs.
- Big rocks are done, still some issues to address
- KERIpy
- Branch release-1.1.0-rc.1 with corresponding PyPi pre-release
- KERIA
- Branch release-0.1.0-rc.1 with corresponding PyPi pre-release
- 4 issues wrt API endpoints that contain
/identifiers/{name} that is not used- Will merge before release
- Signifypy
- Branch release-0.1.0-rc.1 with corresponding PyPi pre-release
- Signify-TS
- Branch release-0.1.0-rc.1
- Phil Feairheller TODO: figure out how to publish a pre-release in NPM
- CESRide integration branch closed and moved to fork, thanks Charles Lanahan
- did:webs
- Tsunami of PRs to finish the identification of normative and informative sections of the spec
- Working on service endpoints section of the spec, missing from current
- cesr-ts
- cesride
- KERIsse
|
| 25 mins | Discussion | Open | - Should KERIpy go to 2.0.0 because of "breaking changes"
- 1.1.0 can be breaking changes according to Samuel Smith
- This is unrelated to KERI CESR version.
- CESR / KERI protocol will go to 2.0 in the new specifications and the reference implementation will follow later this year
- Hoping to reserve 2.0.0 in KERIpy for that update
- PyPi or Docker Container for KERIA
- How to find Transaction Event Log (TEL) of issued/revoked credentials by an AID? (known parameters: issuer AID, wits)
- Do you have the SAID of the credential? - No
- Looking for a list of credentials issued by given issuer
- We have standard messages that are compatible with CESR streams, but no standard APIs within those messages have only been defined ad hoc
- We should probably start defining these APIs
- Daniel Hardman - I don't understand why we would allow an issuer to keep their TEL private. Wouldn't that prevent evaluation of revocation status? If they are willing to assert to the world that facts X, Y, and Z are true (in an ACDC), and if that ACDC is associated with a credential registry, shouldn't they be REQUIRED to expose the TEL so revocation status can be evaluated? Otherwise we have unverifiable data
- Agreed that TEL events should be at least as visible as credentials
- Ed Eykholt - Potential interdependencies between TSP and KERI implementations.
- TSP depends on a CESR implementation and may depend on a KERI implementation if AIDs are being used in a TSP implementation
- Phil Feairheller - I don't believe KERIpy will depend on a TSP implmentation, but issuing for example could be built externally that uses TSP as its transport
|
| 5 mins | Any other business | Open |
|
| 5 mins | - Review decisions/action items
- Planning for next meeting
| Chairs |
|
