At Fri, 27 Jun 2008 10:22:55 -0700, Henry Sinnreich wrote: > > Now help me understand this > > > one of the requirements for running HIP is a rendezvous service. A > > P2PSIP peer protocol is capable of providing the rendezvous service that > > HIP requires to form connections. > > HIP has been defined with a rendezvous server (RVS) in the HIP Rendezvous > Extension RFC 5204. Actually, one of the nicer properties is the > flexibility, since any node can act as a rendezvous server; that's more than > SIP can do. > > What am I missing?
I haven't studies this RFC carefully, but it looks to me like the rendezvous service is potentially distributed, but in the sense that everyone can pick their own rendezvous server, not in the sense that the rendezvous service is collectively provided. This means that I need a real relationship with my RVS (in a similar way that I might have one with my SIP registrar). I need to know that it will be online whenever I am or I will be unreachable. The whole point of a distributed rendezvous service like that provided by P2PSIP is that the various members of the overlay collectively provide that service and as long as one of them is up, the system works, thus removing the need for an explicit service relationship with some server. -Ekr _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
