1. NAT traversal for HIP is described here: http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-04.txt It basically uses ICE.
2. I understand NAT traversal for HIP that uses another approach, not ICE, may be published shortly after testing with SIP VoIP over HIP. See page 9 on http://www3.ietf.org/proceedings/08jul/slides/HIPRG-3.pdf mentioning the testing without changes to SIP VoIP (due to NAT traversal). Henry On 8/13/08 5:57 PM, "shidong chen" <[EMAIL PROTECTED]> wrote: > Hi Henry, > >> 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. > > I briefly checked the HIP. It looks it enable one host to bind to different IP > without interruption of sessions. It is not clear to me how it is related to > NAT crossing issue. Did I miss any great point here? Could you explain how the > idea works here? > > Thanks > > 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
