-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add rendezvous recommendations #302
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 on documenting recommendations. I am not familiar enough with the Rendezvous protocol to approve here. Who is familiar enough to do the review @vasco-santos?
rendezvous/README.md
Outdated
|
||
## Recommendations for Rendezvous Points configurations | ||
|
||
Rendezvous points should have well defined configurations to enable libp2p nodes running the rendezvous protocol to have friendly defaults, as well as to guarantee the security and efficiency of a Rendezvous point. This will be particularly important in a federation, where rendezvous points should share the same expectations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit pick: The rest of the specification is wrapped at 80 characters. Can you do the same here for consistency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
Co-authored-by: Max Inden <mail@max-inden.de>
@vyzo is the author, but I would say that anyone in the interest group can also weight in |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merging here since there have been no concerns raised since the last round of pings. Thanks @vasco-santos.
This PR adds recommendations to the rendezvous spec regarding how a rendezvous point should be configured. These were based on the discussions on the go implementation PR and current code. The discover limit seems a bit higher, but if we have smaller defaults on the client, we can keep it as 1000.
It also fixes an error response status to
E_INVALID_SIGNED_PEER_RECORD
since we are using signed peer records now and this is now yet implemented.