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 15 Next »

Summary:

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.

Date

(7AM Los Angeles, 10AM New York, 3PM London, 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                                                                                                                                                            

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.

Release Status and Work Updates

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

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
    • 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

Future Topics

Action items

  •  

Call Recording

  File Modified




  • No labels