From 4289a95cf175ccac16a9095132714c316f6873ff Mon Sep 17 00:00:00 2001 From: "Matthew A. Miller" Date: Sun, 20 Jul 2014 14:13:35 -0400 Subject: [PATCH] XEP-0343 v0.2 - Add optional explicit signaling of channels to the transport element. --- xep-0343.xml | 59 +++++++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 54 insertions(+), 5 deletions(-) diff --git a/xep-0343.xml b/xep-0343.xml index aa5834ab..aee66b59 100644 --- a/xep-0343.xml +++ b/xep-0343.xml @@ -4,13 +4,14 @@ WebRTC Data Channel Protocol WebRTC Data Channel Protocol <http://tools.ietf.org/html/draft-jesup-rtcweb-data-protocol-04>." > +WebRTC 1.0: Real-time Communication Between Browsers WebRTC 1.0: Real-time Communication Between Browsers <http://www.w3.org/TR/2013/WD-webrtc-20130910/>." > RFC 3758 RFC 3758: Stream Control Transmission Protocol (SCTP) Partial Reliability Extension <http://tools.ietf.org/html/rfc3758>." > %ents; ]>
- Use of DTLS/SCTP in Jingle ICE-UDP + Signaling WebRTC datachannels in Jingle 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. &LEGALNOTICE; 0343 @@ -24,12 +25,18 @@ - NOT_YET_ASSIGNED + jingle-webrtc-datachannels Jens Bavendiek bavendiek@dbis.rwth-aachen.de + + 0.2 + 2014-07-15 + ph +

Add optional explicit signaling of channels to the transport element.

 + 0.1 2014-01-23 @@ -123,10 +130,22 @@ ]]>

As seen in the example, there is no notion about DataChannel internals. The only things negotiated here are the port on which the SCTP Stream runs and the name of the DataChannel. Further negotiation is happening through the &webrtc-protocol;, thus the DataChannel is identified through the content name.

+

For some uses like negotiated datachannels, it might be required to explicitly signal the channel properties. This is done by including a <channel/> element qualified by the 'urn:xmpp:jingle:transports:webrtc-datachannel:0' namespace &VNOTE; as child of the &TRANSPORT; for each channel that has to be signaled. An abbreviated example follows:

+ + + + + + [...] + ]]> -

The values and names for the &SCTPMAP; element are taken from the corresponding SDP. The attributes of the <sctpmap/> element are as follows.

- +

The values and names for the &SCTPMAP; element are taken from the corresponding SDP. The attributes of the <sctpmap/> element are as follows.

+
@@ -152,6 +171,7 @@
Name Description16
+

The attributes of the <channel/> element map directly to the attributes of the RTCDataChannelInit dictionary as defined in &w3-webrtc-draft;.

As described in XEP-0166, to acknowledge receipt of the session initiation request, the responder immediately returns an IQ-result.

@@ -258,6 +278,7 @@

This specification defines the following XML namespace:

  • urn:xmpp:jingle:transports:dtls-sctp:1
    • +
  • urn:xmpp:jingle:transports:webrtc-datachannel:0

The ®ISTRAR; includes the foregoing namespace in its registry at &NAMESPACES;, as governed by &xep0053;.

 @@ -290,7 +311,7 @@ The protocol documented by this schema is defined in - XEP-xxxx: http://www.xmpp.org/extensions/xep-xxxx.html + XEP-0343: http://www.xmpp.org/extensions/xep-0343.html @@ -305,7 +326,35 @@ + + + + + + The protocol documented by this schema is defined in + XEP-0343: http://www.xmpp.org/extensions/xep-0343.html + + + + + + + + + + + + + + + + + ]]>