You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: