2020-04-22-A Aries Working Group Call (AMER morning)

Summary:

• Plans for IIW
• Work updates
• Plan for future meetings
• IOT best practices

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

Date

22 Apr 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                                                                                                                                                            

• Mike Richardson (EuroLedger) <emerysolutions@yahoo.co.uk>
• George Aristy (SecureKey) <george.aristy@securekey.com>
• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Robert Mitwicki The Human Colossus Foundation <robert.mitwicki@humancolossus.org>

Welcome / Introductions

Announcements

• IIW April 28-30
• Mttr's proposal for a different approach to ZKPs

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
  • One agent under test
  • Issue, credential, and proof tests are merged.
• Aries Agent Test Harness
  • Test compatibility between any two agents 
  • https://github.com/bcgov/aries-agent-test-harness​_
• Aries Shared:
  
  • indy-vdr (Andrew Whitehead)  https://github.com/hyperledger/indy-vdr
    • Nearing release 1.0(?) - most work complete that was needed: Design doc, FFI, testing, CI / CD
      • CD not there
      • No design doc, but crate docs
    • As an Aries interface becomes standardized, will add that API layer
      • Do we hold off on setting the version until this is in place.  Maybe 0.8
    • GitHub actions runs unit tests and basic integration tests
    • VON Network browser moved to Indy-VDR instead of LibIndy (no wallet needed because it is stateless)
      • Andrew working a refactor in a PR
  • indy-credx - https://github.com/andrewwhitehead/indy-credx
    • need to move ASAP to at least BC Gov repo - Andrew Whitehead
    • ACA-Py branch created that can do credential exchange with indy-credx
    • Next up: adding revocation 2.0 support
    • Integrating upgraded PyO3 library
  • indy-shared-rs - https://github.com/bcgov/indy-shared-rs
    • Shared features across indy-vdr and indy-credx
    • pack/unpack on Ursa (not libsodium)
    • home for revocation support?  Or at least shared set membership proof handling?
  • aries-credx
    • https://github.com/sovrin-foundation/aries-credx-framework-rs
      • 6 most common attribute encodings
      • Does not have anoncreds 1 attribute encoding.
    • Can make a non-revocable credential and create proofs.
      • Tagging will be moved to the KMS.
      • Mike will be working on revocation registry 2.0
  • Aries Secure Storage initiatives:
    • Mike working on documentation and architecture as an Aries RFC (KMS architecture) and Ursa RFC (API)
      • PR is submitted: https://github.com/hyperledger/aries-rfcs/pull/440
    • Mike and Cam's work aries-kms-mayaguez - repo?  features?
      https://github.com/sovrin-foundation/aries-kms-rs
      • Persistence work allows plugging in any database engine.
      • Focus is using an external enclave.
      • Working on Postgres storage; will need help on lox
      • Something out the end of the week.
• Aries-CloudAgent-Python (bc.gov)
  • Release 0.5.0 is on PyPi.
  • Revocation support added and tested with Streetcred and esatus Mobile Agents; major/minor version handling
• Aries-Framework-Go (Troy) #aries-go
  • Implementing the Out-Of-Band protocol
  • Implementing issue-credential and present-proof protocols
• 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
  • Converted to a web application by Robert Mitwicki - repo https://github.com/thclab/aries 
• Aries-SDK-Java
• Aries-Framework-JavaScript
  • Started regular meetings: Framework JS Meetings
  • Current focus is on mediator use case (NodeJS)
• Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
• Aries-MobileAgent-Xamarin
  • Evolution of the open source mobile agent (Mattr Global's OSMA)
  • https://github.com/hyperledger/aries-mobileagent-xamarin
• Ursa
  • 0.4.0 scheduled for late March
    • Improved hash to curve algorithm
    • Updates to AMCL wrapper
  • To replace libsodium, need to have a replacement for the anoncrypt / authcrypt sealed box for pack / unpack.
    • Can be done in Ursa with two steps, but might add as a single function call.

RFC Progress

Other Business

Future of this meeting

• We recognize as a community that each of us needs to adapt to current global events: improving the upstream open source libraries is likely to be slower.
  • No apology is needed if people take longer to respond to things.
  • Richard's role changed, so we need a change in host.
    • Robert Mitwicki will coordinate the meeting going forward
  • Fewer meetings and more async collaboration?

IOT best practices by Robert Mitwicki (cc Adam Burdett , Lohan Spies )

• Presentation slides:
• 
  
  • "Data is like electricity, it has value when it flows." - Michael Corning 
    • IoT is all about data flows, and SSI enables those flows.
• Sovrin SSI in IOT working group
  • https://sovrin.org/event/sovrin-ssi-for-iot-task-force-meeting-22/
  • ssiot@sovrin.org
• SSIMeetup:
  • Corporates and IoT
  • Machine Identity
• Static Agents
  • https://github.com/hyperledger/aries-staticagent-python
  • Hyperledger Mentorship 2019: Raspberry Pi Indy Agent

Future Topics

• Next Meeting
• Other:
  
  • 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
  • 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