From 1c13444a832475bf29405a3b7106819b91a98140 Mon Sep 17 00:00:00 2001 From: stpeter Date: Thu, 24 Mar 2011 11:46:44 -0600 Subject: [PATCH] initial version of XEP-0293 --- inbox/rtcp-fb.xml => xep-0293.xml | 33 ++++++++++++++++--------------- 1 file changed, 17 insertions(+), 16 deletions(-) rename inbox/rtcp-fb.xml => xep-0293.xml (94%) diff --git a/inbox/rtcp-fb.xml b/xep-0293.xml similarity index 94% rename from inbox/rtcp-fb.xml rename to xep-0293.xml index a706446f..ac0d0948 100644 --- a/inbox/rtcp-fb.xml +++ b/xep-0293.xml @@ -12,9 +12,9 @@ Protocol (RTCP)-Based Feedback (RTP/AVPF) with Jingle RTP sessions &LEGALNOTICE; - xxxx - ProtoXEP - Standard + 0293 + Experimental + Standards Track Standards Council @@ -28,7 +28,13 @@ olivier.crete@collabora.co.uk jingle - + + 0.1 + 2011-03-24 + psa +

Initial published version.

+
+ 0.0.1 2011-01-10 oc @@ -46,8 +52,7 @@

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

  1. Enable negotiations of the required parameters for the - transmissions of RTP Feedback messages as defined in RFC - 4585.
  2. + transmissions of RTP Feedback messages as defined in &rfc4585;.
  3. Map these parameters to Session Description Protocol (SDP; see &rfc4566;) to enable interoperability.
@@ -56,8 +61,8 @@

This specification defines two new elements, <rtcp-fb/> and <rtcp-fb-trr-int/>, that can be inserted in the - <description/> or the <payload-type/> elements of a - XEP-0167 RTP session. The presence of any of these elements in a + <description/> or the <payload-type/> elements of + &xep0167;. The presence of any of these elements in a content's description means that the RTP/AVPF profile should be used for the whole content. If any of these elements are inside the <payload-type/> element, the parameters specified apply only to @@ -134,7 +139,7 @@ milliseconds for this media session. It corresponds to the

The responder MUST send any <rtcp-fb/> element as-is if it accepts it. It MUST NOT change any parameter to conform the the - negotiation defined in RFC 4585 Section 4. It MUST NOT add any + negotiation defined in RFC 4585 Section 4. It MUST NOT add any <rtcp-fb/> element that was not offered by the initiator. It MUST NOT modify the 'value' of any >rtcp-fb-trr-int/< element. It can only remove the >rtcp-fb-trr-int/< element or @@ -145,7 +150,7 @@ milliseconds for this media session. It corresponds to the <rtcp-fb-trr-int/> element, then this value is "0".

Example negotiation where the initiator requests Packet Loss - Indications (pli) as defined in RFC 4585 on both H.263 and H.264, + Indications (pli) as defined in RFC 4585 on both H.263 and H.264, but also requests Slice Loss Indications for H.264 with a minimum interval between regular full compound RTCP packets of 100 milliseconds.

@@ -322,11 +327,7 @@ milliseconds for this media session. It corresponds to the registry at &NAMESPACES;, as governed by &xep0053;.

-

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;
@@ -336,4 +337,4 @@ milliseconds for this media session. It corresponds to the

Thanks to Youness Alaoui for his feedback.

- \ No newline at end of file +