Bruce Lowekamp wrote:
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).
Actually, in HIP you don't need a separate "registration server" to get
rendezvous service but you use the registration extension (RFC5203) to
register to the service. And for the NATed case you should use HIP relay
service, i.e., instead of forwarding just the I1 as in RVS, whole base
exchange is done trough the relaying service. This service can be
provided by a relay server [1] or, e.g., a P2PSIP overlay [2].
Cheers,
Ari
[1] http://tools.ietf.org/html/draft-ietf-hip-nat-traversal-03#section-3.1
[2] http://tools.ietf.org/html/draft-camarillo-hip-bone-01#section-3.2
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
