Skip to content
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.

Transport Return Route Protocol (RFC 0092) #858

Closed
rolsonquadras opened this issue Nov 22, 2019 · 2 comments
Closed

Transport Return Route Protocol (RFC 0092) #858

rolsonquadras opened this issue Nov 22, 2019 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@rolsonquadras
Copy link
Contributor

Implement Transport Return Route Protocol in Aries Framework Go - https://github.com/hyperledger/aries-rfcs/tree/master/features/0092-transport-return-route.

@rolsonquadras rolsonquadras changed the title Implement Transport Return Route Protocol Implement Transport Return Route Protocol (RFC 0092) Nov 25, 2019
@rolsonquadras
Copy link
Contributor Author

rolsonquadras commented Nov 25, 2019

Implementation of this protocol can be broken down into following issues:

  1. Get access to sender verification key in Inbound transport (To store the transport based on verKey) - Inbound Transport handler - Access to Sender Verification Key #876
  2. Support to configure framework with Transport return route option - To add values to the transport decorator.
  3. Make the transport duplex - Use the stored transport based on the verKey of the recipient
    (sender in case of inbound) during outbound calls - DIDComm Transport(WS) - Support Duplex communication #877
  4. BDD tests - Transport Return Route RFC - BDD Tests #893

@fqutishat fqutishat added the enhancement New feature or request label Nov 26, 2019
@fqutishat fqutishat added this to the 0.1.1 milestone Nov 26, 2019
@rolsonquadras rolsonquadras changed the title Implement Transport Return Route Protocol (RFC 0092) Transport Return Route Protocol (RFC 0092) Dec 2, 2019
@rolsonquadras
Copy link
Contributor Author

Core framework support is implemented as part of PR #896.

Remaining issues for completing basic e2e implementation - #877 #893

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants