mirror of
https://github.com/vacp2p/specs.git
synced 2026-01-09 07:17:56 -05:00
chore: replace peerInfo by signed peer record
This commit is contained in:
@@ -14,6 +14,7 @@ Interest Group: [@daviddias], [@whyrusleeping], [@Stebalien], [@jacobheun], [@yu
|
||||
[@Stebalien]: https://github.com/Stebalien
|
||||
[@jacobheun]: https://github.com/jacobheun
|
||||
[@yusefnapora]: https://github.com/yusefnapora
|
||||
[@vasco-santos]: https://github.com/vasco-santos
|
||||
|
||||
See the [lifecycle document][lifecycle-spec] for context about maturity level
|
||||
and spec status.
|
||||
@@ -69,7 +70,6 @@ number of rendezvous points can federate using pubsub for internal
|
||||
real-time distribution, while still providing a simple interface to
|
||||
clients.
|
||||
|
||||
|
||||
## The Protocol
|
||||
|
||||
The rendezvous protocol provides facilities for real-time peer
|
||||
@@ -77,7 +77,8 @@ discovery within application specific namespaces. Peers connect to the
|
||||
rendezvous point and register their presence in one or more
|
||||
namespaces. It is not allowed to register arbitrary peers in a
|
||||
namespace; only the peer initiating the registration can register
|
||||
itself.
|
||||
itself. The register message contains a serialized [signed peer record]()
|
||||
created by the peer, which can be validated by others.
|
||||
|
||||
Peers registered with the rendezvous point can be discovered by other
|
||||
nodes by querying the rendezvous point. The query specifies the
|
||||
@@ -195,16 +196,10 @@ message Message {
|
||||
E_UNAVAILABLE = 400;
|
||||
}
|
||||
|
||||
message PeerInfo {
|
||||
optional bytes id = 1;
|
||||
repeated bytes addrs = 2;
|
||||
}
|
||||
|
||||
message Register {
|
||||
optional string ns = 1;
|
||||
optional PeerInfo peer = 2;
|
||||
optional bytes signedPeerRecord = 2;
|
||||
optional int64 ttl = 3; // in seconds
|
||||
optional bytes signedPeerRecord = 4;
|
||||
}
|
||||
|
||||
message RegisterResponse {
|
||||
|
||||
Reference in New Issue
Block a user