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 (Employer) <email>
Troy Ronda (SecureKey) <troy.ronda@securekey.com>
John "Jack" Callahan (Veridium) <jcallahan@veridiumid.com>
Matt Raffel (Kiva) <mattr@kiva.org>
Ken Ebert (Sovrin Foundation) <ken@sovrin.org>
Stephen Curran (Cloud Compass/BC Gov) <swcurran@cloudcompass.ca>
Sergey thinks we need an overview of how the many protocols fit together.
Other Business
Payments in Aries
Currently have the payment decorator defines how to request payment and prove that payment happened (same information as the W3C Web Payments standard).
Protocol gap in actually making the payment. Should be pluggable (application agnostic).
Payments are defined as part of credential issuance and presentation
Top level concept like KMS?
Using hardware enclaves (Mike L.)
Agent KMS Considerations:
Steve M. has played a lot with the Apple enclave and can help.
Tension between security of a hardware enclave, and the portability promises of SSI.
Assumption is that any key put into an enclave cannot come out.
Ursa will provide an interface for interacting with an enclave (abstract the complexity).