From e8f8de2743edbfc53fa6d19327a6f305baf8ba7d Mon Sep 17 00:00:00 2001
From: stpeter Initial published version. This documents specifies how to negotiate the use of the RTP
- Header Extensions as defined by RFC 5285 with Jingle RTP
+ Header Extensions as defined by &rfc5285; with Jingle RTP
sessions. The Jingle extension defined herein is designed to meet the following requirements:
@@ -110,8 +116,8 @@ inside the <rtp-hdrext/> element.
Example negotiation where the initiator offers to use the - timestamp offset header extension as defined in RFC 5450 and also - the requests synchronisation metadata header extension (RFC 6051) + timestamp offset header extension as defined in &rfc5450; and also + the requests synchronisation metadata header extension (&rfc6051;) with either the 56-bit or the 64-bit format.
The <rtp-hdrext/> element maps to the "a:extmap=" SDP line - defined in RFC 5285. The ID is mapped to the 'id' attribute, the + defined in RFC 5285. The ID is mapped to the 'id' attribute, the direction to the 'senders' attribute and the URI to the 'uri' attribute.
-Example conversion of a incomplete sample fragment of a SDP taken from RFC 5285 section 6 into equivalent XMPP:
+Example conversion of a incomplete sample fragment of a SDP taken from RFC 5285 section 6 into equivalent XMPP:
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.
+ &NSVER;