One approach to assure NAT traversal for all application protocols,
including various P2P overlays is using the Host Identity Protocol (HIP).

With such an approach, not all the media has to pass through VPN-like
servers.
A small number of bootstrap nodes that are not behind NAT can act as relays
for those nodes are behind ³bad² NAT.

Docs and code are available at http://infrahip.hiit.fi/
The openHIP from Boeing is also available at
http://hipserver.mct.phantomworks.org/

HIP implementation is required only in the peers and does not require any
change to the OS.
It is similar to the ³user space VPN² from the openVPN. No IP network
support is required either.

It is not funny to watch how without HIP every application developer has to
reinvent NAT traversal...
Not to mention mobility and multi-homed network problems.

Henry


On 8/13/08 3:06 PM, "shidong chen" <[EMAIL PROTECTED]> wrote:

> Hello,
> When I try to implement udp or tcp hole punching in real world (e.g.
> bittorrent), an scalability issue pops up.
> UDP/TCP hole punching
> Hole punching requires peer A and B to sent packet to each other almost "at
> same time" to build the connection. It also requires server S keep a UDP/TCP
> connection with "every" peer to forward connection request. It could be very
> costly to build such a server S to serve millions of peers. Any solution?
> It looks to me the connection request forwarding could be standardized into a
> P2P control protocol (besides the data transfer protocols). could anyone tell
> me if there is an effort to standardize this (a draft version is great too)?
> 
> Greatly appreciated If you could point me to any document, source code,
> library or examples on implementation of hole punching.
> 
> Thanks a lot,
> 
> Shidong
> 
> 
> _______________________________________________
> p2p-hackers mailing list
> [email protected]
> http://lists.zooko.com/mailman/listinfo/p2p-hackers

_______________________________________________
p2p-hackers mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/p2p-hackers

Reply via email to