From 17b5f2148644caf5b923ebfb1b3531e776f95761 Mon Sep 17 00:00:00 2001
From: David Laban <david.laban@collabora.co.uk>
Date: Mon, 7 Mar 2011 18:14:13 +0000
Subject: Be less wrong about RTCPMinimumInterval=0

---
 spec/Call_Content_Media_Description_Interface_RTCP_Feedback.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'spec/Call_Content_Media_Description_Interface_RTCP_Feedback.xml')

diff --git a/spec/Call_Content_Media_Description_Interface_RTCP_Feedback.xml b/spec/Call_Content_Media_Description_Interface_RTCP_Feedback.xml
index 4b493b38..6be37093 100644
--- a/spec/Call_Content_Media_Description_Interface_RTCP_Feedback.xml
+++ b/spec/Call_Content_Media_Description_Interface_RTCP_Feedback.xml
@@ -46,9 +46,9 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
         <tp:docstring>
           The minimum interval between two regular RTCP packets in
           milliseconds for this content. If no special value is desired, one
-          should put MAXUINT (0xFFFFFFFF). In most profiles, the special value
+          should put MAXUINT (0xFFFFFFFF). In RTP/AVPF, the special value
           0 means "Do not let RTCP packets exceed 5% of the available
-          bandwidth."
+          bandwidth". Other profiles may assign other meanings to the value 0.
         </tp:docstring>
       </tp:member>
       <tp:member type="a(sss)" tp:type="RTCP_Feedback_Message[]"
-- 
cgit v1.2.3