Summary:
| Excerpt |
|---|
|
...
(7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)
| Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.  |
|---|
Attendees
- Sam Curren(Indicio) <sam@indicio.tech>
- Alexandra Walker (Indicio) <alex.walker@indicio.tech>
- bruce_conrad@byu.edu (Pico Labs) <bruce_conrad@byu.edu>
- Lance Byrd (RootsID) <lance.byrd@rootsid.com>
- James Ebert (Indicio) <james.ebert@indicio.tech>
- Warren Gallagher (AffinitiQuest) <warren@affinitiquest.io>
Welcome / Introductions
Announcements
...
- Peer DID Continued Discussion
- https://hackmd.io/_Kkl9ClTRBu8W4UmZVGdUQ?view#Base-DID-method-support
- Review of general sentiment
- did:kerilite update? - Rodolfo
- define shorter 'synonym' for did:peer:2 dids that can be computed by both sides, used interchangeably after initial exchange.
- did:peer:3 (really, 2.1, or 2 with synonym)
- Issue Credential Protocol Short Circuit
- Daniel to make issue.
- Issue: https://github.com/hyperledger/aries-rfcs/issues/774
- Next Steps:
- Survey of existing impls? Do they care if the proceeding messages happen?
- New version - based on didcomm v1 or v2?
- IssueCredential 4.0
- contains DIDComm v2 compatible attachments (from IssueCredential 3.0)
- also .1 and .2 features from IssueCredential v2.x
- consider other protocol updates as well.
- Diagram source link: https://github.com/hyperledger/aries-rfcs/blob/main/features/0036-issue-credential/credential-issuance.html (instructions in .md text for 0036)
- PR Needed
- PR 775 - OCA
- Three things without consensus
- 1 - pushback on the image slice
- unhappy with ux compared to first option
- 2 - need command line interface that converts source oca to an oca bundle
- have a utility that converts the xls file
- json file merged in for the arise specific stuff
- SAID (from keri) that are embedded in the resulting file that do not meet spec.
- May be able to ignore the SAID problem.
- to fully follow OCA spec we need to fill that gap.
- that's the goal of the command line utility
- 3 - how does the issuer/schema publisher publish the bundle? (Discovery)
- Tails file like server?
- Cred Def points to tails file
- OCA bundle doesn't have that.
- Schema / Cred Def can't point to it directly.
- Supplement
- As link
- As inline attachment
- Works like a one-shot link
- Malicious issuer could make link unique per issuer to monitor access
- requires presentation supplement to make it available to verifier
- possibly workable but not ideal
- OCA bundle (similar to cred def) that could be used
- network (indy/chekd/etc) publish oca bundle alongside cred def
- automation to include when cred def / schema retrieved
- Use the repository (could be Github) strategy that can be accessed by convention
- locate in repo by issuerid and schemaid
- Could have a common OCA repository used for lookup
- could tolerate multiple repositories
- governance rules matter for each repository
- acceptance / rejection policy
- github allows process
- github privately owned
- stopgap solution, easy to create but not awesome in the long term
- links from governance files
- needs some sharing from Indicio to aid understanding
- Tails file like server?
- 1 - pushback on the image slice
- Next Steps:
- Merge? Update?
- Three things without consensus
- Issue Credential v2.1 Learning
- Why is this hard?
- no post-mortem yet
- fixes could be had in the proposed 4.0
- parallel message delivery in a protocol is hard?
- Will revisit after BCGov postmortem
- Issue 773 - Mime type inconsistency
...