/
2019-12-03 Framework Go Weekly Planning

2019-12-03 Framework Go Weekly Planning

Dec 10, 2019

Summary:

Planned topics

  • Work updates (5 mins)

  • Grooming (20 mins)

  • Design discussion (20 mins)

  • Open Discussion (10 mins)

Date

Dec 3, 2019 (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>

  • @Sandra Vrtikapa (SecureKey)

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

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

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

  • @Baha A Shaaban (SecureKey)

  • @Filip Burlacu (SecureKey)

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

Welcome / Introduction

Announcements

  • None

Release status

  • None

Work updates (from the previous week)

  • Implicit Invitation: REST API #897(@Sandra Vrtikapa)

  • Implicit Invitation: Go sdk enable invitee to specify own did for connection  #892 (@Sandra Vrtikapa)

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

  • Introduce - finish state machine #883 @Андрій Солук

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

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

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

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

  • Draft RFC for HTTP over DIDComm tunnel (@Filip Burlacu)

  • Draft Aries RFC-0335 for JWE envelopes FIPS/NIST compliant (@Baha A Shaaban )

Grooming updates (from the previous week)

  • High level tasks breakdown for DIDComm Router/Mediator #807 - @Rolson Quadras

Design discussion

  • Design Crypto/KMS Issue 913 (@Filip Burlacu @Baha A Shaaban)

Milestone progress

  • TBD

Other business

  • TBD

Upcoming work

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

  • Design/Implementation of Route Coordination Protocol (RFC 0211) #837 - @Rolson Quadras

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

  • Introduce refactoring (need to discuss with @George Aristy ) @Андрій Солук

  • Refactoring creation of serialized JWT from Verifiable Credential #339 @Dmitriy Kinoshenko

Future topics

  • TBD

Action items

Groom FIPS compliant, JWE compliant Packer (@Baha A Shaaban , @Filip Burlacu )
Groom HTTP tunneling over DIDComm (@Filip Burlacu , @Baha A Shaaban )
DIDAuthZ RFC and groom stories (@George Aristy @Sandra Vrtikapa )