So, I've implemented and have been working with this in stanza.io (a new JS websocket XMPP client lib) for WebRTC signaling. (Don't worry, I'm also working with Fippo to get proper Jingle to work too).
The primary benefit to this is that I don't have to parse SDP in the browser to create Jingle stanzas, and then translate Jingle back to SDP. However, what is documented here doesn't go far enough to provide that benefit -- it still requires some SDP parsing on the receiving end to extract the relevant bits needed for WebRTC. So, what I've been using has the form: <message> <sox xmlns="http://stanza.io/protocol/sox"; sid="..." type="offer|answer|candidate" [label="..." id="..."]> ...SDP blob... </sox> </message> Where sid is the user generated session ID, and label and id are for ICE candidate updates. The browser APIs helpfully provide the label and id values. Since they are included as attributes, there is no need for parsing the SDP blob by the receiver. -- Lance On Jun 12, 2013, at 1:55 PM, XMPP Extensions Editor <[email protected]> wrote: > The XMPP Extensions Editor has received a proposal for a new XEP. > > Title: SIP/SDP Over XMPP (SoX) > > Abstract: This specification defines an XMPP protocol extension for > communicating Session Description Protocol (SDP) data, along with relevant > Session Initiation Protocol (SIP) headers. The SoX protocol is designed for > use by XMPP-only endpoints that need to communicate raw SDP information > (e.g., in WebRTC scenarios), not as a general-purpose replacement for the > XMPP Jingle extensions. > > URL: http://xmpp.org/extensions/inbox/sox.html > > The XMPP Council will decide in the next two weeks whether to accept this > proposal as an official XEP. >
