From e8f8de2743edbfc53fa6d19327a6f305baf8ba7d Mon Sep 17 00:00:00 2001 From: stpeter Date: Thu, 24 Mar 2011 11:47:00 -0600 Subject: [PATCH] initial version of XEP-0294 --- inbox/rtp-hdrext.xml => xep-0294.xml | 34 +++++++++++++++------------- 1 file changed, 18 insertions(+), 16 deletions(-) rename inbox/rtp-hdrext.xml => xep-0294.xml (91%) diff --git a/inbox/rtp-hdrext.xml b/xep-0294.xml similarity index 91% rename from inbox/rtp-hdrext.xml rename to xep-0294.xml index ef902588..628c747d 100644 --- a/inbox/rtp-hdrext.xml +++ b/xep-0294.xml @@ -11,14 +11,14 @@ the use of the use of RTP Header Extension as defined by RFC 5285 with Jingle RTP sessions &LEGALNOTICE; - xxxx - ProtoXEP - Standard + 0294 + Experimental + Standards Track Standards Council XEP-0167 - RFC 85 + RFC 5285 Olivier @@ -27,7 +27,13 @@ olivier.crete@collabora.co.uk jingle - + + 0.1 + 2011-03-24 + psa +

Initial published version.

+
+ 0.0.1 2011-01-10 oc @@ -37,7 +43,7 @@

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.

@@ -45,7 +51,7 @@

The Jingle extension defined herein is designed to meet the following requirements:

  1. Enable negotiations of the RTP Header extensions as defined in - RFC 5285.
  2. + RFC 5285.
  3. Map these parameters to Session Description Protocol (SDP; see &rfc4566;) to enable interoperability.
@@ -110,8 +116,8 @@ inside the <rtp-hdrext/> element.

if it is "initator" or "responder".

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.

@@ -159,11 +165,11 @@ inside the <rtp-hdrext/> element.

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;