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

Compare with Current View Page History

« Previous Version 29 Next »

Summary:

Planned topics

  • Work updates (5 mins)
  • Grooming (20 mins)
  • Design discussion (20 mins)
  • Open Discussion (10 mins)

Date

 (7:30AM Los Angeles, 10:30AM Toronto/New York, 3:30PM London, 17:30H 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

  • None

Release status

  • None

Work updates (from the previous week)

  • Protocol Service eventing implementation in progress (Rolson Quadras )
  • Selection criteria RFC (done) (George Aristy )
  • Consent Receipts (in discovery) (George Aristy )
  • State Actions-Requested/Refactor Destination for sending outbound messages (Peer Review)
  • Create default Implementation for Wallet CreateKey (Firas Qutishat )
  • Set ServiceEndpoint value from InboundTransport (Firas Qutishat )
  • Create Pack() for Authcrypt logic (Firas Qutishat )
  • Authcrypt Encrypt updated with JWK this weekend - work will resume to update the format (Baha A Shaaban )
  • Added all remaining controller API endpoints including exchange request/response workflow (Sudesh Shetty )
  • Improvement of Verifiable Credential model extension. On-going work on JSON Web Token proof of Verifiable Credential (Dima)

Grooming updates (from the previous week)

Design discussion

  1. What to persist in the storage ?
    1. Encryption before storage
  2. DID Exchange Flow - Wiki/Issue #258 (Rolson Quadras ) 
  3. Options for crypto/envelope interop with agents using libsodium: (Filip Burlacu  / Baha A Shaaban )
    1. Convince other agents to switch from EC 25519 (Ed25519 signing, salsa/chacha encrypt) to more mature alternatives
    2. Port the functions needed from libsodium to native golang
    3. Introduce libsodium dependency (using GoKillers/libsodium-go wrapper)
    4. If libsodium is in some way incompatible/out of compliance with IETF specs (eg with chacha), get them to update, and convince other agents using libsodium to update

Milestone progress

  • No updates.

Other business

  • None.

Future topics

Action items

  • No labels