Peter Saint-Andre 6 years ago
parent
commit
8fff70b813
1 changed files with 16 additions and 9 deletions
  1. 16
    9
      xep-0266.xml

+ 16
- 9
xep-0266.xml View File

@@ -11,6 +11,7 @@
11 11
   &LEGALNOTICE;
12 12
   <number>0266</number>
13 13
   <status>Draft</status>
14
+  <interim/>
14 15
   <type>Standards Track</type>
15 16
   <sig>Standards</sig>
16 17
   <approver>Council</approver>
@@ -23,6 +24,12 @@
23 24
   <shortname>N/A</shortname>
24 25
   <discuss>jingle</discuss>
25 26
   &stpeter;
27
+  <revision>
28
+    <version>1.1rc1</version>
29
+    <date>2013-03-01</date>
30
+    <initials>psa</initials>
31
+    <remark><p>Updated to reflect standardization of the Opus codec; changed client conformance to also recommend (but not require) support for Opus.</p></remark>
32
+  </revision>
26 33
   <revision>
27 34
     <version>1.0</version>
28 35
     <date>2011-10-04</date>
@@ -92,7 +99,7 @@
92 99
 </header>
93 100
 
94 101
 <section1 topic='Introduction' anchor='intro'>
95
-  <p>&xep0167; defines the &xep0166; signalling exchanges needed to establish voice chat and other audio sessions using the Real-time Transport Protocol &rfc3550;; however, it does not say which audio codecs are mandatory-to-implement, since the state of codec technologies is more fluid than the signalling interactions. This document fills that gap by providing guidance to Jingle developers regarding audio codecs.</p>
102
+  <p>&xep0167; defines the &xep0166; signalling exchanges needed to establish voice chat and other audio sessions using the Real-time Transport Protocol &rfc3550;; however, it does not specify which audio codecs are mandatory-to-implement, since the state of codec technologies is more fluid than the signalling interactions. This document fills that gap by providing guidance to Jingle developers regarding audio codecs.</p>
96 103
   <p>Because codec technologies are typically subject to patents, the topics discussed here are controversial. This document attempts to steer a middle path between (1) specifying mandatory-to-implement technologies that realistically will not be implemented and deployed and (2) providing guidelines that, while realistic, do not encourage the implementation and deployment of patent-clear technologies.</p>
97 104
 </section1>
98 105
 
@@ -127,7 +134,7 @@
127 134
     </table>
128 135
   </section2>
129 136
   <section2 topic='Opus' anchor='codecs-opus'>
130
-    <p>The Opus codec is under development within the IETF's <link url='http://tools.ietf.org/wg/codec/'>Codec Working Group</link>. In essence it combines the best features of CELT (developed by Jean-Marc Valin, the creator of Speex) and SILK (created by and widely used in the Skype service). The following table summarizes the available information about Opus.</p>
137
+    <p>The Opus codec was developed within the IETF's <link url='http://tools.ietf.org/wg/codec/'>Codec Working Group</link> and has been published as &rfc6716;. In essence it combines the best features of CELT (developed by Jean-Marc Valin, the creator of Speex) and SILK (created by and widely used in the Skype service). The following table summarizes the available information about Opus.</p>
131 138
     <table caption='Codec Considerations for Opus'>
132 139
       <tr>
133 140
         <th>Quality</th>
@@ -136,10 +143,10 @@
136 143
         <th>Patents</th>
137 144
       </tr>
138 145
       <tr>
139
-        <td>Extremely high quality; can be used for wide-band audio.</td>
146
+        <td>Extremely high quality; can be used for wide-band audio; very robust in the face of packet loss.</td>
140 147
         <td>See &opusrtp;.</td>
141
-        <td>Covered under IETF IPR rules, the intent is for the codec to be covered under a simplified BSD license. See <link url='http://tools.ietf.org/html/draft-ietf-codec-opus'>http://tools.ietf.org/html/draft-ietf-codec-opus</link> for details. Not commonly deployed yet, but the SILK codec on which it is partly based is very widely deployed.</td>
142
-        <td>Designed to be patent-clear, but IPR claims have been filed.</td>
148
+        <td>In accordance with IETF IPR rules, the codec is covered under a simplified BSD license. See RFC 6716 for details. Starting to be more commonly deployed, and the SILK codec on which it is partly based is very widely deployed.</td>
149
+        <td>Designed to be patent-clear, although IPR claims have been filed.</td>
143 150
       </tr>
144 151
     </table>
145 152
   </section2>
@@ -164,13 +171,13 @@
164 171
 
165 172
 <section1 topic='Guidance for Implementers' anchor='impl'>
166 173
   <p>This section is non-normative.</p>
167
-  <p>Given that both Speex and G.711 are patent-clear, freely implementable, and commonly deployed, implementers are encouraged to consider including support for both codecs in audio applications of Jingle RTP sessions. Discussion on the jingle@xmpp.org mailing list indicates a slight preference for G.711 because it is easily available and so widely deployed (e.g., in SIP networks and the PSTN). The Opus codec is not yet widely deployed (or even fully developed), but it might become the "codec of the future" for audio applications over the Internet.</p>
174
+  <p>Given that Opus and G.711 are patent-clear, freely implementable, and commonly deployed, implementers are encouraged to consider including support for both codecs in audio applications of Jingle RTP sessions. Discussion on the jingle@xmpp.org mailing list indicates a slight preference for G.711 because it is easily available and so widely deployed (e.g., in SIP networks and the PSTN). Opus has effectively superseded Speex, and implementers are strongly encouraged to include support for Opus rather than Speex among the "open" codecs.</p>
168 175
 </section1>
169 176
 
170 177
 <section1 topic='Mandatory-to-Implement Codecs' anchor='mti'>
171
-  <p>As of June 2011, this document makes the following recommendations:</p>
178
+  <p>As of January 2013, this document makes the following recommendations:</p>
172 179
   <ol>
173
-    <li>Jingle clients MUST implement both PCMU and PCMA.</li>
180
+    <li>Jingle clients MUST implement G.711 (i.e., both PCMU and PCMA) and SHOULD implement Opus.</li>
174 181
     <li>Gateways between Jingle networks and other networks (e.g., SIP networks and the PSTN) MUST implement either PCMU or PCMA (and preferably both).</li>
175 182
   </ol>
176 183
   <p>Naturally, clients and gateways can implement additional codecs, such as those listed in this document.</p>
@@ -189,6 +196,6 @@
189 196
 </section1>
190 197
 
191 198
 <section1 topic='Acknowledgements' anchor='ack'>
192
-  <p>Thanks to Olivier Crête, Dave Cridland, Florian Jensen, Justin Karneges, Evgeniy Khramtsov, Marcus Lundblad, Tobias Markmann, Pedro Melo, Jack Moffitt, Jeff Muller, Jehan Pagès, Arc Riley, Kevin Smith, Remko Tronçon, Justin Uberti, and Paul Witty for their feedback.</p>
199
+  <p>Thanks to Olivier Crête, Dave Cridland, Florian Jensen, Justin Karneges, Evgeniy Khramtsov, Marcus Lundblad, Tobias Markmann, Jean-Marc Valin, Pedro Melo, Jack Moffitt, Jeff Muller, Jehan Pagès, Arc Riley, Kevin Smith, Remko Tronçon, Justin Uberti, and Paul Witty for their feedback.</p>
193 200
 </section1>
194 201
 </xep>

Loading…
Cancel
Save