Bruce,
On Mar 14, 2008, at 7:48 AM, Bruce Lowekamp wrote:
I guess the exception could be some overlay configuration where
only a certain # of nodes are allowed to be full peers and so some
perfectly capable nodes are relegated to client status... But I
don't see this as a usual config.
Actually, this is very common. In global-scale p2p overlays (like
skype), it's typical to have a requirement that only public (at
least non-filtered) nodes can become peers, and
Sure. And I completely agree that for large-scale P2PSIP clouds,
we'll have similar issues. When I was writing this note I was
thinking of primarily smaller environments.
it is also quite common to limit the number of peers because if the
storage requirements of the overlay aren't that great, allowing the
number of peers to grow unbounded only serves to increase the
average path length.
Good point.
I highly recommend reading draft-pascual-p2psip-clients-01 for its
very long list of why a node might not be a peer.
I did before writing this. It's a good document.
2. If (per #1) client nodes are not running STUN/TURN services, it
is not clear to me how another client behind a NAT would *find*
another client node to act as a relay - but maybe I need some more
caffeine to think that through....
Broadcast/multicast is probably the easiest way to find another
device.
But how do you broadcast/multicast through a firewall? i.e. how does
a node behind a FW or NAT use broadcast/multicast to find other clients?
(As Song suggests, this could be done by the bootstrap server or
enrollment server.)
Also, STUN and TURN are very different. Every node has to run STUN
to support ICE. TURN is entirely another matter....
Agreed.
Regards,
Dan
--
Dan York, CISSP, Director of Emerging Communication Technology
Office of the CTO Voxeo Corporation [EMAIL PROTECTED]
Phone: +1-407-455-5859 Skype: danyork http://www.voxeo.com
Blogs: http://blogs.voxeo.com http://www.disruptivetelephony.com
Build voice applications based on open standards.
Find out how at http://www.voxeo.com/free
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
