[Standards] Proposed XMPP Extension: Jingle ICE Transport Method

Lance Stout lancestout at gmail.com
Thu Dec 17 16:10:24 UTC 2015


Regarding the <ice-gathering-complete/> end-of-candidates signal:

> <iq from='juliet at capulet.example/yn0cl4bnw0yr3vym'
>     id='xv39z423'
>     to='romeo at montague.example/dr4hcr0st3lup4c'
>     type='set'>
>   <jingle xmlns='urn:xmpp:jingle:1'
>           action='transport-info'
>           initiator='romeo at montague.example/dr4hcr0st3lup4c'
>           sid='a73sjjvkla37jfea'>
>     <content creator='initiator' name='this-is-the-audio-content'>
>       <ice-gathering-complete xmlns='urn:xmpp:jingle:transports:ice:info:0'/>
>     </content>
>   </jingle>
> </iq>


Placing a new element as a direct child of <content/> is a bit more difficult for an implementation to process (it requires a new special case to look for it as opposed to being carried along in the <transport/> element data already). It also would be better to drop the :info: namespace and just include it in the new ice:0 namespace, especially since there is already the remote-candidate signal.


So something like:

> <iq from='juliet at capulet.example/yn0cl4bnw0yr3vym'
>     id='xv39z423'
>     to='romeo at montague.example/dr4hcr0st3lup4c'
>     type='set'>
>   <jingle xmlns='urn:xmpp:jingle:1'
>           action='transport-info'
>           initiator='romeo at montague.example/dr4hcr0st3lup4c'
>           sid='a73sjjvkla37jfea'>
>     <content creator='initiator' name='this-is-the-audio-content'>
>       <transport xmlns='urn:xmpp:jingle:transports:ice:0'>
>         <gathering-complete />
>       </transport>
>     </content>
>   </jingle>
> </iq>



- Lance


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4115 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20151217/c5af6185/attachment-0001.bin>


More information about the Standards mailing list