[Standards] UPDATED: XEP-0167 (Jingle Audio via RTP)

Tim Julien tjulien at limewire.com
Wed May 21 18:57:42 UTC 2008

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 9.2, 9.3.

However, Jingle (166) is very clear that content-replace cannot be used 
in the PENDING state.

Section 9.4 also makes use of content-replace in the PENDING state in a 
slightly different way - during transport negotiations as opposed to as 
a final step.

-Tim Julien

XMPP Extensions Editor wrote:
> Version 0.17 of XEP-0167 (Jingle Audio via RTP) has been released.
> Abstract: This specification defines a Jingle application type for negotiating a voice chat or other audio session. The application type uses the Real-time Transport Protocol (RTP) for the underlying media exchange and provides a straightforward mapping to Session Description Protocol (SDP) for interworking with SIP media endpoints.
> Changelog: Corrected use of content-replace action per XEP-0166. (psa)
> Diff: http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0167.xml?r1=1707&r2=1715
> URL: http://www.xmpp.org/extensions/xep-0167.html

More information about the Standards mailing list