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
- Name (organization) <email>
Welcome / Introductions
Announcements
- None
Release status
- None
Work updates (from the previous week)
- Protocol Service eventing implementation in progress (Rolson)
- Selection criteria RFC (done) (George)
- New RFC 0214: help-me-discover
- New RFC 0217: linkable-message-paths
- Small tweak to RFC 0028: introduce in PR #219
- Consent Receipts (in discovery) (George)
- State Actions-Requested/Refactor Destination for sending outbound messages (Peer Review)
- Create default Implementation for Wallet CreateKey (Firas)
- Set ServiceEndpoint value from InboundTransport (Firas)
- Create Pack() for Authcrypt logic (Firas)
Grooming updates (from the previous week)
- Verification #96 groomed (Filip / Sandra)
Design discussion
- What to persist in the storage ?
- Encryption before storage
- DID Exchange Flow - Wiki/Issue #258 (Rolson)
- Options for crypto/envelope interop with agents using libsodium: (Filip/Baha)
- Convince other agents to switch from EC 25519 (Ed25519 signing, salsa/chacha encrypt) to more mature alternatives
- Port the functions needed from libsodium to native golang
- Introduce libsodium dependency
Milestone progress
- TBD
Other business
- TBD
Future topics
- TBD
Action items
- TBD