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

Route Coordination Protocol (RFC 0211) #837

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

Route Coordination Protocol (RFC 0211) #837

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

Comments

@rolsonquadras
Copy link
Contributor

rolsonquadras commented Nov 19, 2019

Issue to track the design of a WASM Agent interacting with a server agent through Router.

Agent registration pre-process:

  1. Router creates a random WS endpoint and supplies this info to the agent. eg ws://agent-server.com/uuid/mailbox
  2. Agent knows the routers endpoint(ws)/DID/Invitation.
  3. Agent connects to the router WS endpoint and does DIDExchange. Puts it's endpoint as something derived from ws://agent-server.com/uuid/<>

The outcome is that the agent DID has claimed a UUID on the router. Any interaction for that UUILD have to be authenticated by the agent DID. Now we can do all the route registration steps and agent can use that endpoint (http) to communicate with other agents.

@troyronda troyronda added the enhancement New feature or request label Nov 20, 2019
@troyronda troyronda added this to the 0.1.1 milestone Nov 20, 2019
@rolsonquadras rolsonquadras changed the title DIDComm Router Design Route Coordination Protocol (RFC 0211) Dec 2, 2019
@rolsonquadras
Copy link
Contributor Author

@rolsonquadras
Copy link
Contributor Author

Base structure for Route Coordination protocol is added as part of #934. Enhancement and each feature implementation will be added as part of separate Issues.

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