2020-03-11-A Aries Working Group Call (AMER morning)

Summary:

Planned:

• Work updates
• Evernym approach to connection reuse in LibVCX
• Architecture for Aries KMS

Note: This call is Recorded. Recordings posted at the bottom of the page.

Date

11 Mar 2020 (7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)

Remember the Hyperledger Code of Conduct

Anti-Trust Policy:

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

Attendees                                                                                                                                                            

• Michael Lodder (Sovrin Foundation) <mike@sovrin.org>
• Stephen Curran (Cloud Compass/BC Gov) <swcurran@cloudcompass.ca>
• Ken Ebert Ken Ebert (Sovrin Foundation) <ken@sovrin.org>
• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Marvin Berstecher (esatus AG) <m.berstecher@estaus.com>
• Nikita Khateev (DSR) <nikita.khateev@dsr-corporation.com>
• Echo Harker (Evernym) <echo.harker@evernym.com>
• @Kumaravel N (Ford) <nkumara2@ford.com>
• Darko Kulic (Evernym) <darko.kulic@evernym.com>
• Steve McCown (Anonyome Labs) <smccown@anonyome.com>

Welcome / Introductions

Announcements

• Hyperledger Diversity, Civility, and Inclusivity Survey
• IIW April 28-30

Related Calls

• Previous Aries Working Group calls
• DIF DIDComm WG Call: Rolling Agenda.
• Identity Implementors Working Group call
  • Main place to get project updates, release status, and announcements.

Release Status and Work Updates

• Aries Protocol Test Suite
  • Issue, credential, and proof tests are merged.
• Aries Shared:
  • indy-vdr (Andrew Whitehead) https://github.com/hyperledger/indy-vdr
    • Remaining work: Design doc, FFI, testing, CI / CD
    • As an Aries interface becomes standardized, will add that API layer
  • indy-credx and aries-credx
    • https://github.com/sovrin-foundation/aries-credx-framework-rs
      • Generic APIs that are pluggable
      • Test vectors for interop
    • https://github.com/andrewwhitehead/indy-credx
  • Aries-Shared-Util
    • Pack / Unpack
    • Not started yet
  • Aries-KMS
    • Mike Lodder working on documentation and architecture as an Aries RFC (KMS architecture) and Ursa RFC (API)
      • Differs from Indy Wallet architecture by separating out auth and access control. Intention is to ensure a smooth transition from Indy.
      • Ability to export keys under certain conditions (metadata is set upon key creation)
    • Mike and Cam's aries-core-rs → aries-mayaguez
      https://github.com/sovrin-foundation/aries-kms-rs
      • Evolution from lox
      • Will include a default storage that is not a different implementation from the plugins
    • Indy wallet crate might move to start another aries-kms implementation → aries-kms-vostok
• Aries-CloudAgent-Python (bc.gov)
  • Release 0.4.5 is on PyPi.
  • Revocation support has merged into master and is likely to included in the next release. Some smoothing of the edges happening.
    • Note: uses anoncreds 1.0 (hence, tails files) and so will be constrained in use cases to those with small numbers of credentials (e.g. ~25k per RevReg.
• Aries-Framework-Go (Troy) #aries-go
  • Enable common JavaScript API for both WASM and REST controller APIs.
  • Verifiable Credential controller APIs (validation and storage).
  • Preparing 0.1.2 release
• Aries-SDK-Ruby (Jack)
  • Added DID/Verkey sign_and_submit to aries_sdk_ruby and published new gem (0.0.8)
  • Created aries-rails-docker experiment that support Rails 4 with Indy 1.8.1 on Heroku & Dokku
• Aries-Framework-DotNet (Tomislav)
  • Release last week for Aries compatibility with ACApy and LibVCX (RFC 0094)
• Aries-StaticAgent-Python
• Aries-Toolbox
  • Added basic message admin
  • Working on a getting started video
• Aries-SDK-Java
• Aries-Framework-JavaScript / Aries-SDK-JavaScript
  • Started regular meetings: Framework JS Meetings
• Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
• Ursa
  • 0.3.2 released in February, includes key exchange methods (can replace libsodium)

RFC Progress

Other Business

• Evernym approach to connection reuse in LibVCX Sergey Minaev and Darko Kulic
  • When a connection request is received, if the public DID matches an existing connection, it responds with a connection redirect message to the existing connection.
  • https://github.com/hyperledger/indy-sdk/pull/2080
• Aries KMS design Mike Lodder
  • Architecture RFC
  • 3rd party libraries we could leverage:
    • Google Tink as an encryption library used in the KMS for aries-framework-go

Future Topics

• Next Meeting
• Other:
  
  • Formal verification (Sven Hammann)
  • Where should we document interoperability results (AIP 1.0)? A page in this wiki space?
  • Hubs vs Agents
    • https://www.hyperledger.org/blog/2019/07/23/rhythm-and-melody-how-hubs-and-agents-rock-together
  • Status and future of wallet query language
  • IOT best practices (Robert Mitwicki, Adam Burdett , Lohan Spies )
  • DID Resolution W3C and Sam's concerns: https://github.com/hyperledger/aries-rfcs/issues/130
  • Architecture of Aries Verifiable Credentials Proof Formats (Mike Lodder)

Action items

Call Recording