Posted by galato
on August 29, 2010 at 9:59 AM PDT
if this is not documented anywhere (in specs or otherwise) can anyone shed some
light on the details?
Peer A, behind a NAT let's say, will connect to a RDV
and send its info to it - what kind of info is this?
If it generates a server pipe and it advertises it with
the RDV, what kind of info does it send then? Do either of
these contains routing information?
Peer B, also behind a NAT, will contact the RDV to find
Peer A's server pipe. What does it get as information?
When does it realize that Peer B may not directly accessible
and it will need to go through a relay to find it? And
does Peer A need to have contacted the relay with its info
so that it knows where it is and it has a route to it?
The reason I am asking this is that I have the RDV and RLY both
residing in the public domain. Is it beneficial to have a relay
dedicated for each edge Peer behind a NAT advertising the public
IP of the corresponding router so that remote peers can find it?
Or is a public RLY a better soln?