Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary:

Excerpt

Planned

  • Work updates
  • Aries crypto service RFC
  • Progress on POCs for Aries Core libraries: aries-kms and aries-vdri

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

...

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                                                                                                                                                            

Welcome / Introductions

Announcements

Related Calls

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

...

  • Aries Protocol Test Suite
      Works, and ready for test contributions
    • Progress in making it work with the LibVCX Dummy Cloud Agent (support for mediators).
    • Ready for people to contribute additional tests.
  • Aries-KMS
    • Moving Indy Wallet crate into aries-ams / aries-kms (might change the repo name)
    • cam's rust aries-kms (just old code in repo right now, once I add more to my RFC I will focus my attention to adding code here)
    • SQLite as the default wallet.
    • aries-ams-sqlite is archived
    • Need to migrate Postgres wallet plugin from Indy to aries-ams-postgres
    • Working on aries-kms RFC 
  • Verifiable Data Registry Interface library
    • Static Peer DIDs in aries-vdri as the default implementation
    • aries-vdri-peer is archived
    • Ken's POC
  • Other Core Libraries (pack / unpack)
  • Aries-CloudAgent-Python (bc.gov) - Latest is Release 0.3.5 on PyPi
  • Aries-Framework-Go (Troy) #aries-go
  • Aries-SDK-Ruby (Jack)
  • Aries-Framework-DotNet (Tomislav)
  • Aries-StaticAgent-Python - Now up to 0.6.1; more details
  • Aries-Toolbox
    • Moving repos to HyperLedger's Github Org.
    • ACApy plugin for supported admin protocols.
  • Aries-SDK-Python - Wrapper from JeromK and SBCA?
  • Aries-SDK-Java
  • Aries-SDK-JavaScript
    • PR for moving Indy NodeJS wrapper repo has been merged into https://github.com/hyperledger/aries-framework-javascript
    • Repo is ready for contributors to start picking next tasks
    • Need to rename existing repo - "aries-framework-javascript" to "aries-sdk-javascript" and create a new repo as "aries-framework-javascript"
    • Regular weekly zoom calls to be scheduled from this Friday. Will share the details on Rocket Chat.
    • DIF people interested in implementing a Java Script library that might share some of the functionality of the Aries SDK. We need to keep that in mind.
  • Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
  • Migration from LibIndy
    • Closing PRs related to Indy wrappers with pointers to Aries language libraries
    • LibVCX support for some Aries protocols
  • 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

...

  • 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

Other Business

  • Crypto Service RFC, Robert Mitwicki
    • Expose cryptographic services outside of the Agent (e.g. make available for document transfer services).
    • https://github.com/mitfik/aries-rfcs/tree/master/features/0312-crypto-service
    • Overlap Next steps with the RFC:
      • Need to address overlap with Aries-KMS.
      • Need to address key exposure post-compromise.
        • Leverage message blinding. (Mike L can help)
      • Include more use cases
        • more specific details (PDF viewer . . . )
        • concern that the process is driven outside the agent, instead of by the agent
        • explain when the compromises in trust-shifting makes sense
        • where is this useful, and where is this not recommended
  • Progress on POCs for Core Libraries: Aries-KMS, Aries-VDRI

...