Initial published version approved by the XMPP Council.
0.0.12013-11-25ph
First draft.
RFC 5888RFC 5888: The Session Description Protocol (SDP) Grouping Framework <http://tools.ietf.org/html/rfc5888>. defines a framework to group SDP 'm' lines for different purposes. A mapping to Jingle as an extension to Jingle (XEP-0166)XEP-0166: Jingle <https://xmpp.org/extensions/xep-0166.html>. is defined in this document.
It is anticipated that the primary use of this is with the draft-ietf-mmusic-sdp-bundle-negotiationNegotiating Media Multiplexing Using the Session Description Protocol (SDP) <https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-bundle-negotiation/>. Work in progress. framework used in WebRTC.
The SDP format defined in RFC 5888 is shown below.
a=group:semantics identification-tag
An example follows.
a=group:LS voice webcam
This SDP attribute is translated to Jingle as a <group/> element qualified by the 'urn:xmpp:jingle:apps:grouping:0' namespace, as shown below. The semantics is mapped to a 'semantics' attribute. The identification-tags are mapped to content elements whose name attribute is set to the identification-tag.
]]>
An example follows.
]]>
The <group/> element is included as child of the <jingle/> element.
[ ... ]
[ ... ]
]]>
Note: the identification-tags correspond to the <content/> 'name' attributes. These in turn map to the 'mid' attribute in SDP.
If an entity supports the grouping framework described in RFC 5888, it MUST advertise that fact in its responses to Service Discovery (XEP-0030)XEP-0030: Service Discovery <https://xmpp.org/extensions/xep-0030.html>. information ("disco#info") requests by returning a feature of 'urn:ietf:rfc:5888':
]]>
]]>
In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in Entity Capabilities (XEP-0115)XEP-0115: Entity Capabilities <https://xmpp.org/extensions/xep-0115.html>.. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.
Thanks to Emil Ivov and Lance Stout for their feedback.
The XML format for this specification originates from libjinglelibjingle is now part of the WebRTC Native Code Package available from webrtc.org..
This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA)The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>..
This specification defines the following XML namespace:
urn:xmpp:jingle:apps:grouping:0
The XMPP RegistrarThe XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>. includes the foregoing namespace to the registry located at <https://xmpp.org/registrar/namespaces.html>, as described in Section 4 of XMPP Registrar Function (XEP-0053)XEP-0053: XMPP Registrar Function <https://xmpp.org/extensions/xep-0053.html>..
If the protocol defined in this specification undergoes a revision that is not fully backwards-compatible with an older version, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.