RTP draft: chair review
diff --git a/doc/draft-ietf-payload-rtp-opus.xml b/doc/draft-ietf-payload-rtp-opus.xml
index f14e69e..7f1f867 100644
--- a/doc/draft-ietf-payload-rtp-opus.xml
+++ b/doc/draft-ietf-payload-rtp-opus.xml
@@ -18,7 +18,7 @@
<!ENTITY nbsp " ">
]>
- <rfc category="std" ipr="trust200902" docName="draft-ietf-payload-rtp-opus-06">
+ <rfc category="std" ipr="trust200902" docName="draft-ietf-payload-rtp-opus-07">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
@@ -71,7 +71,7 @@
</address>
</author>
- <date day='6' month='January' year='2015' />
+ <date day='13' month='January' year='2015' />
<abstract>
<t>
@@ -221,7 +221,7 @@
<t>
The bitrate can be adjusted at any point in time. To avoid congestion,
the average bitrate SHOULD NOT exceed the available
- network capacity. If no target bitrate is specified, the bitrates specified in
+ network bandwidth. If no target bitrate is specified, the bitrates specified in
<xref target='bitrate_by_bandwidth'/> are RECOMMENDED.
</t>
@@ -269,7 +269,7 @@
DTX can be used with both variable and constant bitrate.
It will have a slightly lower speech or audio
quality than continuous transmission. Therefore, using continuous
- transmission is RECOMMENDED unless restraints on network capacity
+ transmission is RECOMMENDED unless restraints on available network bandwidth
are severe.
</t>
@@ -414,7 +414,7 @@
</t>
<texttable anchor='opus-packetization' title="Supported Opus frame
- sizes and timestamp increments">
+ sizes and timestamp increments marked with an o. Unsupported marked with an x.">
<ttcol align='center'>Mode</ttcol>
<ttcol align='center'>fs</ttcol>
<ttcol align='center'>2.5</ttcol>
@@ -433,20 +433,20 @@
<c>2880</c>
<c>voice</c>
<c>NB/MB/WB/SWB/FB</c>
- <c></c>
- <c></c>
<c>x</c>
<c>x</c>
- <c>x</c>
- <c>x</c>
+ <c>o</c>
+ <c>o</c>
+ <c>o</c>
+ <c>o</c>
<c>audio</c>
<c>NB/WB/SWB/FB</c>
+ <c>o</c>
+ <c>o</c>
+ <c>o</c>
+ <c>o</c>
<c>x</c>
<c>x</c>
- <c>x</c>
- <c>x</c>
- <c></c>
- <c></c>
</texttable>
</section>
@@ -613,7 +613,9 @@
</list></t>
<t>Interoperability considerations: none<vspace blankLines='1'/></t>
- <t>Published specification: none<vspace blankLines='1'/></t>
+ <t>Published specification: RFC [XXXX]</t>
+ <t>Note to the RFC Editor: Replace [XXXX] with the number of the published
+ RFC.<vspace blankLines='1'/></t>
<t>Applications that use this media type: </t>
<t><list style="hanging">
@@ -623,6 +625,8 @@
media streaming.</t>
</list></t>
+ <t>Fragment identifier considerations: N/A<vspace blankLines='1'/></t>
+
<t>Person & email address to contact for further information:</t>
<t><list style="hanging">
<t>SILK Support silksupport@skype.net</t>
@@ -646,7 +650,7 @@
<t>Jean-Marc Valin jmvalin@jmvalin.ca<vspace blankLines='1'/></t>
</list></t>
- <t> Change controller: TBD</t>
+ <t> Change controller: IETF Payload Working Group delegated from the IESG</t>
</section>
<section title='Mapping to SDP Parameters'>