Zoom: https://zoom.us/j/94626752608?pwd=K0t4N3VqRzlscTNYajlxMHNPM08yQT09
Summary:
| Excerpt |
|---|
|
Date
(6AM Los Angeles, 9AM New York, 2PM London, 3PM CET, 17H Moscow)
| Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.  |
|---|
Attendees
- Lance Byrd (RootsID) <lance.byrd@rootsid.com>
Welcome / Introductions
Announcements
Release Status and Work Updates
- Aries Agent Test Harness (https://aries-interop.info)
- Aries Askar secure storage - https://github.com/bcgov/aries-askar
- Frameworks:
- Aries-CloudAgent-Python (https://github.com/hyperledger/aries-cloudagent-python, Meetings: ACA-Pug Meetings)
- Encryption envelope (Askar impl) not fully-developed yet. We could use different libraries (SICPA Rust). SICPA DIDComm impl is what will be used... resolves did peers natively. The keys will have to be transported out of Askar, but that is acceptable for now. SICPA is the most widely used.
- SICPA for DIDComm and did:peer https://github.com/sicpa-dlab/didcomm-python
- No near-term Askar support for the DIDComm v2 encryption envelope and core protocols.
- Protocols related to credential exchange and connection establishment. Distinguish between DIDComm v1 and v2. DID Exchange will be adapted. The main focus is on Out-of-Band protocol.
- Very important to extend the AATH.
- Encryption envelope (Askar impl) not fully-developed yet. We could use different libraries (SICPA Rust). SICPA DIDComm impl is what will be used... resolves did peers natively. The keys will have to be transported out of Askar, but that is acceptable for now. SICPA is the most widely used.
- Aries-Framework-JavaScript (https://github.com/hyperledger/aries-framework-javascript, Meetings: Framework JS Meetings)
- Picos as Aries agents (DIDComm v1: https://github.com/Picolab/aries-cloudagent-pico ; DIDComm v2 work in progress)
- students have returned and they are using SICPA for envelope encryption
- DIF Picos working group, useful for IoT devices
- Swift Framework
- Aries-CloudAgent-Python (https://github.com/hyperledger/aries-cloudagent-python, Meetings: ACA-Pug Meetings)
- Mobile:
- Aries Mobile Agent React Native, aka Aries Bifold (https://github.com/hyperledger/aries-mobile-agent-react-native, Meetings: Aries Bifold User Group Meetings)
- aries-mediator-service – a DIDComm Mediator in a Box
- working on Pickup support
Discussion Topics
Aries Agent Test Harness
Current DIDComm-V2 specific tests:
Code Block title DIDComm-V2 tests aries-agent-test-harness % ./manage tests --tags @DIDComm-V2 Selecting: ['@DIDComm-V2'] Feature: WACI Issuance @T001-IssueCredentialV3 @DIDComm-V2 - WACI issuance flow Feature: DIDComm V2 Establishing Connections @T001-OobV2 @DIDComm-V2 - Establish a connection between two agents using DIDComm V2 Feature: Aries agent present proof v3 @T001-PresentProofV3 @DIDComm-V2 - Present Proof of specific types and proof is acknowledged with a Citizenship credential type with a DID Exchange Connection
- New tag in AATH that are not credential related, maybe DIDCommV2_Peer or DIDCommV2_Simple.
- See https://github.com/tdiesler/aries-agent-test-harness/tree/camel/aries-backchannels/camel#aip-10-status
AIP3
Grand Unified Theory (GUT) Alliance
- Newer than even AIP3.0. KERI and DIDComm v3.0 (likely)
- Link to Daniel’s GUT presentation:
Widget Connector url https://docs.google.com/presentation/d/1ksqVxeCAvqLjr67htWZ4JYaSnI8TUZIO7tDMF5npHTo/edit#slide=id.g138855cddd3_0_9
From our last meeting:
- Apache Camel: https://camel.apache.org/ and we discussed Daniel Hardman's presentation to W3C that talks about classic API/Swagger Endpoints vs. a DIDComm connected ecosystem https://youtu.be/TBxWgNmsnvU
- Our current spreadsheet https://docs.google.com/spreadsheets/d/15noWiG_zhhUpornhrZm9cLEjQ1aa6z9qgJgPCaaIbtY/edit?usp=sharing
- AIP3
- HackMD from the last Aires WG meeting, regarding AIP 3.0
- Great document by Hakan, looking at past AIP definitions and beginning to consider AIP3 definition
- Connectionless DIDComm v2 still needs management of the 'connection' between agents. How should agents handle this?
- Is this worth detailing/discussing or is it just agent specific?
- OOB/handshake/discovery RFP for Aries agents?
- WACI and what the overlap and distinction would be between the AIP and WACI.
- There is some nuance to cred formats you have to support (Indy, BBS+, LD).
- Can we use Discovery protocol to understand the level of WACI support?
- perhaps we need more detailed information from the discovery protocol
- per application protocol supported (formats, messages, crypto).
- Some WACI information to consider https://identity.foundation/waci-presentation-exchange/#format-property.
- Encryption envelope selection
- WACI and what the overlap and distinction would be between the AIP and WACI.
- Bruce Conrad is working with students to implement DIDComm v2 in their Pico environment. Might benefit from JFF work
- DIDComm v2 agent discoverability/interop
- Documentation in terms of Trust Over IP (ToIP) tech stack?
- ACA-PUG
- Libraries for message envelope (Askar, Python impl, Rust impl)