identify: Document identify behavior for asymetrical protocols (#327)

* identify: Document identify behavior for asymetrical protocols

> Note on asymmetrical protocols: Assume an asymmetrical
request-response style protocol `foo` where some clients only support
initiating requests while some servers (only) support responding to
requests. To prevent clients from initiating requests to other clients,
which given them being clients they fail to respond, clients should not
list `foo` in their `protocols` list.

Question emerged in https://github.com/libp2p/specs/issues/324.

* identify/README: Reword to inbound substreams
This commit is contained in:
Max Inden
2021-05-25 17:06:19 +02:00
committed by GitHub
parent 9274d301ba
commit f922a3e4ff

View File

@@ -120,3 +120,11 @@ observable source address.
### protocols
This is a list of protocols supported by the peer.
A node should only advertise a protocol if it's willing to receive inbound
streams on that protocol. This is relevant for asymmetrical protocols. For
example assume an asymmetrical request-response style protocol `foo` where some
clients only support initiating requests while some servers (only) support
responding to requests. To prevent clients from initiating requests to other
clients, which given them being clients they fail to respond, clients should not
advertise `foo` in their `protocols` list.