initial version of XEP-0293

xep-0293.xml

@@ -12,9 +12,9 @@
   Protocol (RTCP)-Based Feedback (RTP/AVPF) with Jingle RTP
   sessions</abstract>
   &LEGALNOTICE;
-  <number>xxxx</number>
+  <number>0293</number>
-  <status>ProtoXEP</status>
+  <status>Experimental</status>
-  <type>Standard</type>
+  <type>Standards Track</type>
   <sig>Standards</sig>
   <approver>Council</approver>
   <dependencies>
@@ -28,7 +28,13 @@
     <jid>olivier.crete@collabora.co.uk</jid>
   </author>
   <discuss>jingle</discuss>
-   <revision>
+  <revision>
+    <version>0.1</version>
+    <date>2011-03-24</date>
+    <initials>psa</initials>
+    <remark><p>Initial published version.</p></remark>
+  </revision>
+  <revision>
     <version>0.0.1</version>
     <date>2011-01-10</date>
     <initials>oc</initials>
@@ -46,8 +52,7 @@
   <p>The Jingle extension defined herein is designed to meet the following requirements:</p>
   <ol>
     <li>Enable negotiations of the required parameters for the
-    transmissions of RTP Feedback messages as defined in RFC
+    transmissions of RTP Feedback messages as defined in &rfc4585;.</li>
-    4585.</li>
     <li>Map these parameters to Session Description Protocol (SDP; see
     &rfc4566;) to enable interoperability.</li>
   </ol>
@@ -56,8 +61,8 @@
 <section1 topic='New elements' anchor='elements'>
   <p>This specification defines two new elements, &lt;rtcp-fb/&gt; and
   &lt;rtcp-fb-trr-int/&gt;, that can be inserted in the
-  &lt;description/&gt; or the &lt;payload-type/&gt; elements of a
+  &lt;description/&gt; or the &lt;payload-type/&gt; elements of 
-  XEP-0167 RTP session. The presence of any of these elements in a
+  &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
   &lt;payload-type/&gt; element, the parameters specified apply only to
@@ -134,7 +139,7 @@ milliseconds for this media session. It corresponds to the
 
   <p>The responder MUST send any &lt;rtcp-fb/&gt; 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 <cite>RFC 4585</cite> Section 4. It MUST NOT add any
   &lt;rtcp-fb/&gt; element that was not offered by the initiator. It
   MUST NOT modify the 'value' of any &gt;rtcp-fb-trr-int/&lt;
   element. It can only remove the &gt;rtcp-fb-trr-int/&lt; element or
@@ -145,7 +150,7 @@ milliseconds for this media session. It corresponds to the
   &lt;rtcp-fb-trr-int/&gt; element, then this value is "0".</p>
 
   <p>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 <cite>RFC 4585</cite> 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.</p>
 
@@ -322,11 +327,7 @@ milliseconds for this media session. It corresponds to the
     registry at &NAMESPACES;, as governed by &xep0053;.</p>
   </section2>
   <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
-    <p>If the protocol defined in this specification undergoes a
+    &NSVER;
-    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.</p>
   </section2>
 </section1>
 <section1 topic='XML Schemas'>