2019-11-26 Framework Go Weekly Planning

2019-11-26 Framework Go Weekly Planning

Summary:

Planned topics

  • Work updates (5 mins)

  • Grooming (20 mins)

  • Design discussion (20 mins)

  • Open Discussion (10 mins)

Date

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

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

  • @Firas Qutishat (Securekey) <firas.qutishat@securekey.com>

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

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

  • @Troy Ronda  (SecureKey) <troy.ronda@securekey.com>

  • @Baha A Shaaban (SecureKey)

  • @Sandra Vrtikapa (SecureKey)

Welcome / Introductions

Announcements

  • None

Release status

  • None

Work updates (from the previous week)

  • Support for IndexedDB #830 - @Firas Qutishat

  • Allow user to inject inbound transport in rest cli #878@Firas Qutishat

  • Allow user to inject multiple outbound transport in rest cli #870@Firas Qutishat

  • Allow user to inject multiple outbound transport #863@Firas Qutishat

  • DIDComm WebSocket Transport #813 #827 - @Rolson Quadras

  • DIDComm Router : Initial Analysis #837 - @Rolson Quadras

  • Error handling in controller REST API #756 @Sudesh Shetty

  • Create public DID in VDRI #845 @Sudesh Shetty

  • Accept Invitation and Accept Exchange request to support public DIDs #871 @Sudesh Shetty

  • BDD tests for DIDexchange with public DIDs using controller - In Progress #796 @Sudesh Shetty

  • Implicit Invitation #817(@Sandra Vrtikapa)

  • Design discussions for issue-credential protocol @Sandra Vrtikapa

  • Introduce - add requesting state to the service (on review) #853 @Андрій Солук

  • Added dependency interface to the Client (Introduce) #724 @Андрій Солук

  • Introduce - replace custom mock with gomock @Андрій Солук

  • Design discussion for issue-credential protocol @derektrider

  • Created a new RFC proposal for request credential flow (on hold) @derektrider

  • Implement client layer for issue-credential flow (holder starts with request) (on hold) #850 @derektrider

  • Understanding verifiable credential and implement service layer for issue credential (on hold) #875 @Talwinder Kaur

  • Refactor creation of VC which extends the base data model #263  (@Dmitriy Kinoshenko )

  • Construct Verifiable Credential object (encoding side) #831 (@Dmitriy Kinoshenko)

  • Add GoDoc documentation with examples to verifiable package #856 - in progress (@Dmitriy Kinoshenko)

 

Grooming updates (from the previous week)

  • Transport Return Route Protocol (RFC 0092) #858@Rolson Quadras

Design discussion

  • DIDAuthZ: resource authorization/discovery

  • Generic tunnels: HTTP over DIDcomm

  • JWE Envelope

Milestone progress

  • TBD

Other business

  • Differentiating between fundamentals and domain-specific payload features. See RFCs#332.

    • How do we indicate what to instantiate when starting the framework? TODO.

  • DID Exchange should have a way to indicate default for simplex vs duplex.

Upcoming work

  • Get destination from the inbound message, add functionality to finish state machine, add validation to the introduce service @Андрій Солук

  • Implementation of Transport Return Route Protocol (RFC 0092) #858 - @Rolson Quadras

  • Update Crypto logic - @Baha A Shaaban @Filip Burlacu

  • Implicit Invitation REST API @Sandra Vrtikapa

  • Add GoDoc documentation with examples to verifiable package #856 (@Dmitriy Kinoshenko)

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

  • Convert Verifiable Credential into Verifiable Presentation #861 (@Dmitriy Kinoshenko)

Future topics

  • TBD

Action items

JWE Envelope RFC and groom stories (@Baha A Shaaban @Filip Burlacu)
Groom routing stories (@Rolson Quadras @Firas Qutishat )
UI components (@Firas Qutishat @Troy Ronda
Higher level agent interface and where does this go (and particularly for UI component planning)?
HTTP tunneling over DIDcomm RFC and groom stories (@Filip Burlacu  @Baha A Shaaban @derektrider @Talwinder Kaur )
DIDAuthZ RFC and groom stories (@George Aristy @Sandra Vrtikapa )
Document remaining plan for Introduce protocol (@Андрій Солук)
Document remaining plan for Verifiable Credentials (@Dmitriy Kinoshenko)