Summary:
Excerpt |
---|
Planned Topics:
|
Note: This call is being recorded.
...
- Issue Game: Can we close this? (15 min -) - issues (as time permits): 290, 77, 225, 122
- Decisions 122 closed, 290 BCGov will pursue, 77 and 225
- Should the ~service decorator be part of AIP 1.0.0? PR link. Richard Esplin
- Evernym reviewed the RFC and discussed the ACApy implementation. Our concerns are resolved.
- New ACApy test showing how a return response endpoint would be routed through two or more mediators.
- Evernym reviewed the RFC and discussed the ACApy implementation. Our concerns are resolved.
- Proposal for adding RFC 348 to AIP 1.0
- Advantages:
- Would start a transition period to the new approach.
- Reduces pressure on the next version of Aries Interop Profile
- Concerns:
- Doesn't seem to fit the scope of AIP 1.0 (define credential exchange in practice today)
- What does it mean to require support of a transitional feature from a compliance perspective?
- Advantages:
- Connection Blues - Continued - Sam Curren/ Stephen Curran
- Using DIDs to use existing invitation
- When an invitation starts from a Public DID, this should be retained by the agent.
- Future invitation Public DIDs can be looked up to see if an existing relationship exists.
- New DID Exchange Message from invitee saying "I'm going to use this existing connection, but exercise a new invitation"
- Connect→Then Invitations
- How to best compose messages?
- Nicely accommodate connectionless messages.
- The Then is more semantically important than the Connection
- Safe URL redirectors
- What to avoid
- Is there a way to do this safely?
- Can we do this with DIDComm? (An Expand Message Protocol?)
- Attachment? (Can fetch from place x), with integrity check and possibly decryption key
- Using DIDs to use existing invitation
- ACApy/Credential F2 Registry HighVolume Performance Testing - Stephen Curran
- Open Discussion / Next Week Topics
...