Skip to content
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.

Revise the relay protocol #68

Closed
raulk opened this issue Apr 6, 2019 · 2 comments
Closed

Revise the relay protocol #68

raulk opened this issue Apr 6, 2019 · 2 comments

Comments

@raulk
Copy link
Member

raulk commented Apr 6, 2019

Carried over from libp2p/go-libp2p#578 (comment):

A relay client can be a consumer of a relay service, or a target of a relayed connection. Currently, all of these flow over the same thick protocol. I really have a hard time wrapping my head around this, and so do our users.

I'd like to segregate this protocol if possible into at least two:

  • /libp2p/circuit/relay/hop/v0.0.0: exposed only by relay nodes. Used inside the initiator -> relay connection.
  • /libp2p/circuit/relay/target/v0.0.0: exposed by clients accepting relayed connections. Used in the relay -> target connection.

This would allow for better implicit observability too. Would've helped a lot in the incident we're analysing.

@raulk raulk mentioned this issue Apr 6, 2019
@Stebalien
Copy link
Member

libp2p/specs#105

@raulk raulk changed the title Segregate the relay protocol Revise the relay protocol Apr 6, 2019
@raulk
Copy link
Member Author

raulk commented Apr 6, 2019

Continuing discussion in libp2p/specs#105.

@raulk raulk closed this as completed Apr 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants