Henry Sinnreich wrote:
On 6/27/08 11:07 AM, "Eric Rescorla" <[EMAIL PROTECTED]> wrote:
As Bruce indicated in a previous message, HIP needs a rendezvous service,
and a generic P2P overlay like RELOAD can provide such a service. In that
respect, HIP would be a client of RELOAD, even if RELOAD itself ran
over ordinary IP.
-Ekr
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?
Locating a capable (non-NATed) rendezvous server in a distributed
environment without a centralized service provider is itself a
non-trivial problem.
Additionally, even if you have obtained a rendezvous server, you still
need a registration server (RFC5203).
A P2PSIP peer protocol provides both.
Bruce
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
