Tim Julien
05-21-2008, 09:04 PM
This makes use of content-replace in the PENDING state (i.e., before
session-accept) as the final step in transport negotiation.
see the state diagrams and examples in sections 5.1, 5.6.
However, Jingle (166) is very clear that content-replace cannot be used
in the PENDING state.
-Tim Julien
XMPP Extensions Editor wrote:
> Version 0.16 of XEP-0176 (Jingle ICE-UDP Transport Method) has been released.
>
> Abstract: This specification defines a Jingle transport method that results in sending media data using raw datagram sockets via the User Datagram Protocol (UDP). This transport method is negotiated via the Interactive Connectivity Establishment (ICE) methodology defined by the IETF and thus provides robust NAT traversal for media traffic.
>
> Changelog: Changed content-modify to content-replace per XEP-0166. (psa)
>
> Diff: http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0176.xml?r1=1539&r2=1716
>
> URL: http://www.xmpp.org/extensions/xep-0176.html
>
session-accept) as the final step in transport negotiation.
see the state diagrams and examples in sections 5.1, 5.6.
However, Jingle (166) is very clear that content-replace cannot be used
in the PENDING state.
-Tim Julien
XMPP Extensions Editor wrote:
> Version 0.16 of XEP-0176 (Jingle ICE-UDP Transport Method) has been released.
>
> Abstract: This specification defines a Jingle transport method that results in sending media data using raw datagram sockets via the User Datagram Protocol (UDP). This transport method is negotiated via the Interactive Connectivity Establishment (ICE) methodology defined by the IETF and thus provides robust NAT traversal for media traffic.
>
> Changelog: Changed content-modify to content-replace per XEP-0166. (psa)
>
> Diff: http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0176.xml?r1=1539&r2=1716
>
> URL: http://www.xmpp.org/extensions/xep-0176.html
>