[Adium-devl] Jingle, Sip and IAX2 in one step

[Alvaro Saurin]

On 9 Nov 2006, at 02:37, Brian West wrote:

>
> On Nov 8, 2006, at 7:31 PM, Alvaro Saurin wrote:
>
>> Well, ICE is not a J/XEPs. ICE is specified in http://www.ietf.org/
>> internet-drafts/draft-ietf-mmusic-ice-05.txt as a set of algorithms
>> for NAT traversal. Some of these algorithms require some kind of
>> negotiations and, in the XMPP/Jingle world, these negotiations are
>> done with the semantics described in the XEP-176. But ICE is not a
>> requirement...
>
> Regardless of what you think ICE is a requirement to speak with any  
> Googletalk client NAT or no NAT.

Brian,

I think ICE it is not required. There is no single line in the XEPs  
where ICE is required for a Jingle implementation. In fact, XEP-0166  
specifies that "possible content transport methods include Real-time  
Transport Protocol (RTP) with Interactive Connectivity Establishment  
(ICE) and raw UDP", and XEP-0177 says that candidate addresses should  
be "derived via prior discovery using RFC 3489 (STUN), which will be  
an address on the outside of the firewall or NAT", but ICE is never  
required in the Jingle specification.

Alvaro

-- 
Alvaro Saurin <alvaro.saurin at gmail.com> <saurin at dcs.gla.ac.uk>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20061109/2b2ac22a/attachment-0001.html>