Page History

...

Release Status and Work Updates

Aries WG
- Presented a comparison of did:keri (lite) and did:peer (algo2... algo1 is used in AFJ)
- Need to do pros/cons spreadsheet comparing the priorities/reqs/community needs
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.
- Aries-Framework-JavaScript (https://github.com/hyperledger/aries-framework-javascript, Meetings: Framework JS Meetings)
  - https://github.com/hyperledger/aries-framework-javascript/pull/1096#issuecomment-1343833016
  - https://github.com/hyperledger/aries-framework-javascript/pull/1211
  - Issue related to multi-base from SICPA for DID peer
- 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, pack/unpack and hopeful sending messages
  - DIF Picos working group, useful for IoT devices.
  - Rich API and Internet connected to be a capable L2 agent.
  - Using Trinsic as VC as a service.
- Swift Framework
- Veramo Framework
  - WACI support https://github.com/uport-project/veramo/issues/1106
  - DID Peer support https://github.com/uport-project/veramo/issues/1105
    - Using Brian's (AviaryTech) DID Peer impl, adapting it as a plugin
      - PR submitted and in review https://github.com/roots-id/didpeer-plugin
  - Merged Mediation, agent can mediate. A Veramo mediator will be published soon.
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
- DIDComm v2 support would probably originate from this meeting/community
AviaryTech DIDComm TS impl
- https://github.com/aviarytech/didcomm
- https://github.com/aviarytech/did-peer
- Focused on OIDC lately
KERI Working Group
- Alternative to peer DID. More refinements to the proposal. Then present it to the Aries groups. Similar to Algo2 of the peer DID.
  - KERI parameter on the DID in order to get the document. Public encryption key and serviceEndpoint.
  - Query param w/ base 64 path that you can decode
    - encryption keys, service endpoint, etc.
    - Compared to did:peer, the keri long form is longer
      - inception event only
      - But follow-on messages only need to use the short-form of KERI DID
    - So, this is not a Persistent did
  - Rodolfo Miranda Will add a README and sample output.
ToIP Trust Spanning Protocol
- Good back and forth between Sam, Daniel, and others https://github.com/trustoverip/trust-spanning-protocol/discussions/17
- Daniel present his proposal this week, at the Wednesday TSPTF
- Sam joins the task force and has a video of Sam's that diagrams his TSP vision https://zoom.us/rec/play/1EcHtXeGPPynwwBvU3X4uAAw0xhFPC3CwwAIXwQ-P_E6tPlzvBskHuzTYftS1ZrmjPw5EiBZWYwiTgdI.tx021j9JATi2l5Xq?continueMode=true&_x_zm_rtaid=noVlj_2fRpuccKG26Jmytw.1675686252575.5cf45b925f44c52d0118a3fdef8541ea&_x_zm_rhtaid=714

Discussion Topics

Thomas - Nessus DIDComm 23.2.0 First Release

Interop Profile

Spreadsheet to compare did peer/keri/key/ etc. pros/cons/needs
- https://hackmd.io/_Kkl9ClTRBu8W4UmZVGdUQ?both
Initial contact through OOB
- DID Doc should contain the endpoint which should establish the connection
Wallet abstraction for AcaPy + Nessus native
Camel Http Endpoint for Nessus agent
Support for RFC0434 Out-of-Band Invitation V1 & V2
Support for RFC0023 Did Exchange V1
Support for RFC0048 Trust Ping V1 & V2
Support for RFC0095 Basic Message V1 & V2
CLI to work with supported protocols and model
Uses SICPA and Walt.id
- Recently accepted PR with SICPA
Will eventually be wrapped in a Camel component, enabling Camel endpoints to support DIDCommV2
- open the doors for adoption from the Camel enterprises

Ecosystem of DIDCommV2 Services or local agents

...

Agents can cache DIDs to know if they have resolved the long-form, etc. This cache needs to be well protected or the conversation is lost.
DIDComm provides a way to rotate Ephemeral DIDs, specifying a new DID (even from a different DID method).

From our last meeting:

Nessus
- Nessus DIDComm 23.2.0 First Release
  - Wallet abstraction for AcaPy + Nessus native
  - Camel Http Endpoint for Nessus agent
  - Support for RFC0434 Out-of-Band Invitation V1 & V2
  - Support for RFC0023 Did Exchange V1
  - Support for RFC0048 Trust Ping V1 & V2
  - Support for RFC0095 Basic Message V1 & V2
  - CLI to work with supported protocols and model
  - Uses SICPA and Walt.id
    - Recently accepted PR with SICPA
  - Will eventually be wrapped in a Camel component, enabling Camel endpoints to support DIDCommV2
    - open the doors for adoption from the Camel enterprises

DIDComm v1 vs v2

https://didcomm.org/book/v2/whatsnew
- simple explanation of the benefits of upgrading
DIDComm v1 is tightly coupled to the Aries RFCs (encryption envelope) and v2 introduces some simplicity in terms of connections

AIP3

HackMD from the last Aires WG meeting, regarding AIP 3.0
Should we specify how the did methods (like did peer) are used?
- We are focused on DIDComm v2 communication but does the rest of the AIP community know that?
- WACI issuance
  - Do you need to be able to resolve indy, cheqd, etc. in order to issue credential
Discussed sub-roles https://raw.githubusercontent.com/hyperledger/aries-rfcs/main/features/0453-issue-credential-v2/credential-issuance.png

Aries Agent Test Harness

What did methods are supported? And how do you configure to use did indy, orb, etc.
What is the priority of tests to create that will eventually be AIP3 tagged tests?
How is mediation tested?
- With the mediation role (what is the name like bob, alice, faber, etc) and show you support the mediation features.

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
- DIDCommV2_Simple
- Didcommv2_base
- Didcommv2_layer2
See https://github.com/tdiesler/aries-agent-test-harness/tree/camel/aries-backchannels/camel#aip-10-status

Grand Unified Theory (GUT) Alliance

There is a warning about did peer on the spec now https://identity.foundation/peer-did-method-spec/
https://daniel-hardman.medium.com/sentries-confessionals-vaults-and-envelopes-4a58cf4f8a5a
original did keri impl https://github.com/WebOfTrust/ietf-did-keri
- Needs to transition to a did keri lite (subset of did keri)
- Signify is a typescript impl that might serve as the the keri lite impl
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

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
Bruce Conrad is working with students to implement DIDComm v2 in their Pico environment. Might benefit from JFF work
DIDComm v2 agent discoverability/interop
- https://identity.foundation/didcomm-messaging/spec/v2.0/#iana-media-types
- https://identity.foundation/didcomm-messaging/spec/v2.0/#discover-features-protocol-20
Documentation in terms of Trust Over IP (ToIP) tech stack?
ACA-PUG
- Libraries for message envelope (Askar, Python impl, Rust impl)

...

Page tree

Versions Compared

Old Version 1

New Version 2

Key

Discussion Topics