2019-12-18-A Aries Working Group Call (US morning)

Summary:

Planned:

• Planning future meetings
• Language wrappers: SDKs and Frameworks
• Resolving different interpretations of Aries RFC 0094.

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

Date

18 Dec 2019 (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                                                                                                                                                            

• Name (Employer) <email>
•  Baha A Shaaban (SecureKey Technologies) <baha.shaaban@securekey.com>
• Tomislav Markovski (Streetcred ID) <tomislav@streetcred.id>
• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Filip Burlacu (SecureKey Technologies) <filip.burlacu@securekey.com>
• Sam Curren (Sovrin Foundation) <sam@sovrin.org>
• Ajay Jadhav (AyanWorks) <ajay@ayanworks.com>
• Troy Ronda  (SecureKey) <troy.ronda@securekey.com>
• Stephen Curran (Cloud Compass/BC Gov) <swcurran@cloudcompass.ca>
• Michael Bernard  (Binus University) <bernardus.kurnia@binuc.ac.id>
• endrefalquier (Spaceman ID) <alexis@spaceman.id>
• George Aristy (SecureKey) <george.aristy@securekey.com>
• Ken Ebert (Sovrin Foundation) <ken@sovrin.org>
• Steve McCown (Anonyome Labs) <smccown@anonyome.com>

Welcome / Introductions

Announcements

• Note the updated calendar invitation on the Hyperledger Calendar
• Hyperledger edX course - Introduction to Hyperledger Sovereign Identity Blockchain Solutions: Indy, Aries & Ursa
• DIF DIDComm WG Call today  US/Mountain. Rolling Agenda.

Related Calls

• Previous Aries Working Group calls
• Identity Implementors Working Group call
  • Main place to get project updates, release status, and announcements.

Release Status and Work Updates

• Aries Protocol Test Suite
• Aries Shared:
  • Aries KMS
  • Verifiable Data Registry Interface (VDRI) library
  • Other Core Libraries (pack / unpack)
• Aries-CloudAgent-Python (bc.gov) - Latest is Release 0.4.0 on PyPi - some internal breaking changes regarding plugins
• Aries-Framework-Go (Troy) #aries-go
  • 2019-12-17 Framework Go Weekly Planning
  • RFC implementation status and Wishlist
  • Continuing efforts on routing & relays, crypto/kms, WebAssembly, generic JSON messages, JWE envelopes.
  • WASM is working for DID Exchange from a browser (running the WASM) to a routing agent. Next we want to show DID Exchange between browsers.
• Aries-SDK-Ruby (Jack)
• Aries-Framework-DotNet (Tomislav)
• Aries-StaticAgent-Python - Now up to 0.6.1; more details
• Aries-Toolbox
• Aries-SDK-Python - Wrapper from JeromK and SBCA?
• Aries-SDK-Java
• Aries-Framework-JavaScript / Aries-SDK-JavaScript
  • As agreed in the connect-a-thon, planning efforts on merging the aries-sdk-javascript codebase into a single framework repo - aries-framework-javascript
  • Starting with the efforts on the React-Native Mobile Agent.
• Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
  • HIPEs/RFCs
    • overview https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0250-rich-schemas
    • context https://github.com/hyperledger/aries-rfcs/tree/master/features/0249-rich-schema-contexts
    • schema processing feedback https://github.com/hyperledger/aries-rfcs/tree/master/features/0281-rich-schemas 
  • Next HIPEs/RFCs for
    • encoding
    • mapping
    • credential definition 
  • Node implementation of
    • context (merged)
    • schema PR in progress https://github.com/hyperledger/indy-node/pull/1513
• Migration from LibIndy
  • LibVCX 0.5.0 with Aries protocol support released today.
• Ursa 0.3.0 release in November
  • Updated BLS signature (multi-signatures, small-BLS)
  • Compilation optimization for specific hardware
  • Rest of predicates for Anoncreds 2.0 and delegatable credentials
  • ZMix 0.1.0 expected in January
    • Ursa and ZMix will be separate releases. ZMix is the proving code, and Ursa is everything else.

RFC Progress

• Rich Schema RFC headed to an APPROVED status, Troy had some comments on how the Link Secrets tie to W3C spec.
• Proposal to renumber RFC 0289
• Progress on JWE envelopes (RFC 334).
• Draft RFCs on Generic JSON Messages and HTTP over DIDComm.

Other Business

• Scheduling future meetings
  • January 1: Cancelled
  • January 15: Need to select a topic
• Aries language wrappers
  • Connect-a-thon proposal: let's only build Frameworks instead of SDKs—let's be opinionated!  Simplify the experience of a new developer.
    • Merge the SDK and the Framework repositories so developers don't have to choose between them.
      • aries-sdk-go should merge into aries-framework-go
      • aries-sdk-javascript should move into aries-framework-javascript
      • other SDKs renamed as Frameworks?
    • Can have a separate SDK artifact in the Framework repository, if desired.
  • When can we deprecate the Indy SDK wrappers?
    • Overlap in development between Indy and Aries. New developers should start in Aries.
    • Hard to maintain CI / CD and do bug fixes for environments and wrappers we don't use.
    • IS-1423 for DotNet, because the Aries Framework is mature.
    • IS-1424 for Java, JavaScript, Android, iOS
    • Challenges with Python
• Misalignment between RFC 0094 and ACA-Py
  • ACA-Py pull request: https://github.com/hyperledger/aries-cloudagent-python/pull/240
  • Evernym products and Pico implemented one way, ACA-Py and DotNetFramework implemented the other. Resolution will be a breaking change.
  • A breaking change will be needed in the near future to implement Tobias' proposed changes to the envelope format.

Future Topics

• Next call
• Other:
  
  • Aries KMS design
    • Define approved algorithms
    • Define plugin interface
    • 3rd party libraries we could leverage:
      • Google Tink as an encryption library
  • Tobias' proposal for evolving DIDComm
  • Use cases for HTTP over DIDComm
  • 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