[Standards] UPDATED: XEP-0343 (Signaling WebRTC datachannels in Jingle)

Ivan Vučica ivan at vucica.net
Wed Jul 23 18:08:48 UTC 2014


Wouldn't it be nicer to promote SCTP to a new transport type instead of
specifying the type to be UDP? An client might ignore the new <sctp/> and
<fingerprint/> elements and assume the offering party is willing to perform
an operation using UDP. Is it an expected situation that, during
negotiation, SCTP might get replaced by unreliable UDP?




On Sun, Jul 20, 2014 at 7:17 PM, XMPP Extensions Editor <editor at xmpp.org>
wrote:

> Version 0.2 of XEP-0343 (Signaling WebRTC datachannels in Jingle) has been
> released.
>
> Abstract: This specification defines how to use the ICE-UDP Jingle
> transport method to send media data using WebRTC DataChannels, so
> technically uses DTLS/SCTP on top of the Interactive Connectivity
> Establishment (ICE) methodology, which provides robust NAT traversal for
> media traffic.
>
> Changelog: Add optional explicit signaling of channels to the transport
> element. (ph)
>
> Diff: http://xmpp.org/extensions/diff/api/xep/0343/diff/0.1/vs/0.2
>
> URL: http://xmpp.org/extensions/xep-0343.html
>
>


-- 
Ivan Vučica
ivan at vucica.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20140723/f95ea8db/attachment.html>


More information about the Standards mailing list