You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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

Welcome / Introductions

Announcements

  • None

Release status

  • None

Work updates (from the previous week)

  • Introduce - implement behavior when introducer stops the protocol #935 #922 Andrii Soluk
  • Introduce - Add validation to the service for incoming messages #890 Andrii Soluk
  • Introduce - add the possibility to pass To structure to the Proposal (on review) #945 Andrii Soluk
  • 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

Grooming updates (from the previous week)


Design discussion


Milestone progress

  • TBD

Other business

  • TBD

Upcoming work

  • Implement logic in did-exchange service for forwarding an invitation and notify introducee after receiving an invitation Andrii Soluk
  • Reply on an inbound message (get destination) & specify senderVerKey on outbound messages Andrii Soluk
  • Route Coordination Protocol (RFC 0211) Implementation in progress #837 - Rolson Quadras

Future topics

  • TBD

Action items

  • TBD
  • No labels