Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Planned:

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

Date

(12PM Los Angeles, 3PM New York, Tuesday at 5AM Sydney)

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 (Organization) <email>
  • John Callahan (Veridium) <jcallahan@veridiumid.com>
  • George Aristy (SecureKey) <george.aristy@securekey.com>

Welcome / Introductions

Announcements

Related Meetings Review

  • Morning Aries Call - Discussion of multiple Proof format handling in Aries; Concrete proposals for moving parts of indy-sdk to aries-sdk - suggestion is wallet code
  • Ursa - off-week - lead up to release happening - release pipeline so that indy can use it.
  • Indy Contributors - 
  • Identity Implementer Call - Tomorrow 8AM Pacific

Upcoming Releases and Work Updates

  • Aries-CloudAgent-Python (bc.gov) - Release 0.3.2 has been tagged and is on PyPi
    • Support for RFC 0036 and RFC 0037 Credential Exchange protocols, 0.1 version of those protocols deprecated
    • Working on next release, particularly on revocation support.
  • Aries-Framework-Go (Troy)
  • Aries-SDK-Ruby (Jack)
    • Released as a Gem (0.0.3) due to Rails 6 issues
    • Developed docker image with Rails 6 (Ruby 2.5.1) with Indy-SDK to test Aries-SDK-Ruby via Dokku deployment
    • Needed for exploring concurrency and compatibility issues with Sidekiq, Resque, SuckerPunch, etc.
  • Aries-Framework-DotNet (Tomislav)
  • Aries-StaticAgent-Python - Release 0.4.0
    • Move from Pysodium → PyNacl
    • Improved module interface and routing.
  • Aries-SDK-Python - Wrapper from JeromK and SBCA?
  • Aries-SDK-Java
    • Aries-SDK subchannel / discussion aries-sdk-java
  • Aries-SDK-JavaScript
    • People are collaborating in the repo.
  • Indy
  • Ursa
    • Working on release of 0.2.0 (September / October)
      • ZKP  / ZKLang improvements
      • Debian packages
      • Refactor internal plumbing for anoncreds 2.0, shouldn't impact external interfaces
      • Refactor multi-signature BLS in addition to aggregated signature
    • Sovrin Foundation is looking to build a Indy specific Ursa,  with ZKPs. Other Aries clients would build a different Ursa

Agenda

  • The DID Spec (and DID Resolution Spec) at the end of the CCG. What is it?  What's in?  What's been left for the WG (if any)? What's next?
  • Changing the namespacing identifier for DIDComm Protocols from did:sov:BzCbsNYhMrjHiqZDTUASHg to something else. aries-rfc#129. Options - did:aries, https, did:git, did:repo
  • How to best talk about Aries interoperability, especially at public forums like IIW?
  • DID-Exchange vs. Connections - aries-rfcs#214 - undo the change?
  • Open Discussion

Next Week

Future Topics

Action items

Call Recording

  File Modified

  • No labels