Some IETF discussion lists (BEHAVE, MMUSIC, SIP) have erupted in controversy over the last few days with regard to ICE. As a result I've been introduced to the concept of UDP hole punching. I think this is the kind of thing that Matt Tucker and Thiago Camargo were talking about months ago on the firstname.lastname@example.org list. Consider:
We'd need a fallback, which would probably be none other than the Jingle ICE Transport Method. But this basic hole-punching technique would be more effective than our current raw UDP method, which right now is the NAT traversal equivalent of the "I'm Feeling Lucky" button in Google search.
Something to think about...
UPDATE: Well, ICE simply is a hole-punching technology, and the right fallback is probably a relay à la TURN. Plus you can't have your XMPP server tell you what your outfacing IP+port is since XMPP runs over TCP, not UDP. So call this post an intriguing idea that won't pan out. BTW, when it comes to open-source ICE libraries, check out libnice.
Peter Saint-Andre > Journal