adding my 2 cents for the comets from scott + It may be nice to upgrade XEP-0215 to discover network servers ( almost same functionality as of DNS SRV ) instead of just stun servers only ( as we discussed early in this list ) so it can look up properly turn servers and ports in some environments .
thanx unni On 8/10/07, Scott Ludwig <[EMAIL PROTECTED]> wrote: > > On Aug 9, 2007 11:01 AM, Thiago Camargo <[EMAIL PROTECTED]> wrote: > > UDP Relays are just simple UDP routers. > > So you can bind Ports and IPs to the clients from your XMPP servers. > > Clients don't need to negotiate directly with Relay Servers(TURN for > instance). > > XMPP Servers can negotiate and allocate the tunnel to be used by the > client. > > > > Check these drafts: > > > > http://www.gliffy.com/publish/1178640/ > > http://www.gliffy.com/publish/1130091/ > > > > Regards, > > Thiago > > I suggest we just use STUN and TURN and get on with this. > > It's true that a special case client can have a special relationship > with a server, and allocate candidates any way it wants, and establish > a standard jingle p2p connection as long as those candidates work as > regular remote candidate for the peer during ICE connectivity > establishment. > > However, it would be nice for any Jingle compatible client to know how > to allocate address candidates from the service it is connected to. To > do this there needs to be standard protocols for discovering and using > these services. It's not complicated. > > Describing N ways to allocate candidates isn't useful for anyone. > There is nothing very special about STUN and TURN technically, except > that they are established and work. Let's use them and move on. >
