2019-12-10 Framework Go Weekly Planning

Planned topics

• Work updates (5 mins)

• Grooming (20 mins)

• Design discussion (20 mins)

• Open Discussion (10 mins)

Dec 10, 2019 (7:30AM Los Angeles, 10:30AM Toronto/New York, 3:30PM London, 17:30H Moscow)

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.

• @Андрій Солук  (Euristiq) <andrii.soluk@euristiq.com>

• @Sandra Vrtikapa (SecureKey)

• @Dmitriy Kinoshenko (Euristiq) <dmytro.kinoshenko@euristiq.com>

• @Rolson Quadras (SeccreKey) <rolson.quadras@securekey.com>

• @George Aristy (SecureKey) <george.aristy@securekey.com>

• None

• None

• Introduce - implement behavior when introducer stops the protocol #935 #922 @Андрій Солук

• Introduce - Add validation to the service for incoming messages #890 @Андрій Солук

• Introduce - add the possibility to pass To structure to the Proposal (on review) #945 @Андрій Солук

• fix: make run-openapi-demo fails #918 @Sandra Vrtikapa  

• Transport Return Route Protocol (RFC 0092) basic flow complete with support for WebSocket and route option "all' #858 - @Rolson Quadras

• Route Coordination Protocol (RFC 0211) Implementation in progress #837 - @Rolson Quadras

• API for protocols to communicate using DIDs, in progress #725 - @Filip Burlacu

• Drafted HTTP over DIDComm RFC, splitting this into two RFCs - @Filip Burlacu

• Verify JWS when creating new presentation #862 @Dmitriy Kinoshenko

• A cache of custom credential schemas of Verifiable Credential #185 @Dmitriy Kinoshenko

• Added design for pluggable interfaces here for Crypto/KMS/JWEBuilder @Baha A Shaaban

• TBD

• TBD

• Implement logic in did-exchange service for forwarding an invitation and notify introducee after receiving an invitation @Андрій Солук

• Reply on an inbound message (get destination) & specify senderVerKey on outbound messages @Андрій Солук

• Route Coordination Protocol (RFC 0211) Implementation in progress #837 - @Rolson Quadras

• Pass VC Test Suite tests #947 @Dmitriy Kinoshenko

• Support JSON-LD for Verifiable Credentials #952 @Dmitriy Kinoshenko

• Linked Data proof of Verifiable Credential #174 - at least start the dev @Dmitriy Kinoshenko

• Drafted HTTP over DIDComm RFC, splitting this into two RFCs @Sudesh Shetty @Filip Burlacu

• Add first integration for Crypto/KMS with Tink @Baha A Shaaban

• TBD