Debian Codegraph @

rfc4788.html

raw
1 <pre>Network Working Group Q. Xie
2 Request for Comments: 4788 Motorola
3 Updates: <a href="./rfc3558">3558</a> R. Kapoor
4 Category: Standards Track Qualcomm
5 January 2007
6
7
8 <span class="h1">Enhancements to RTP Payload Formats for EVRC Family Codecs</span>
9
10 Status of This Memo
11
12 This document specifies an Internet standards track protocol for the
13 Internet community, and requests discussion and suggestions for
14 improvements. Please refer to the current edition of the "Internet
15 Official Protocol Standards" (STD 1) for the standardization state
16 and status of this protocol. Distribution of this memo is unlimited.
17
18 Copyright Notice
19
20 Copyright (C) The IETF Trust (2007).
21
22 Abstract
23
24 This document updates the Enhanced Variable Rate Codec (EVRC) RTP
25 payload formats defined in <a href="./rfc3558">RFC 3558</a> with several enhancements and
26 extensions. In particular, it defines support for the header-free
27 and interleaved/bundled packet formats for the EVRC-B codec, a new
28 compact bundled format for the EVRC and EVRC-B codecs, as well as
29 discontinuous transmission (DTX) support for EVRC and EVRC-B-encoded
30 speech transported via RTP. Voice over IP (VoIP) applications
31 operating over low bandwidth dial-up and wireless networks require
32 such enhancements for efficient use of the bandwidth.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Xie &amp; Kapoor Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
60 <a href="#section-1.1">1.1</a>. Support of EVRC-B Codec . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-1.2">1.2</a>. Compact (Header-free) Bundled Format . . . . . . . . . . . <a href="#page-3">3</a>
62 <a href="#section-1.3">1.3</a>. Discontinuous Transmission (DTX) . . . . . . . . . . . . . <a href="#page-4">4</a>
63 <a href="#section-2">2</a>. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
64 <a href="#section-3">3</a>. EVRC-B Codec . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
65 <a href="#section-4">4</a>. Compact Bundled Format . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
66 <a href="#section-4.1">4.1</a>. Single-Rate Operation . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
67 <a href="#section-5">5</a>. Storage Format for EVRC-B Codec . . . . . . . . . . . . . . . <a href="#page-6">6</a>
68 <a href="#section-6">6</a>. Media Type Definitions . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
69 <a href="#section-6.1">6.1</a>. Registration of Media Type EVRC1 . . . . . . . . . . . . . <a href="#page-6">6</a>
70 <a href="#section-6.2">6.2</a>. Registration of Media Type EVRCB . . . . . . . . . . . . . <a href="#page-9">9</a>
71 <a href="#section-6.3">6.3</a>. Registration of Media Type EVRCB0 . . . . . . . . . . . . <a href="#page-11">11</a>
72 <a href="#section-6.4">6.4</a>. Registration of Media Type EVRCB1 . . . . . . . . . . . . <a href="#page-12">12</a>
73 <a href="#section-6.5">6.5</a>. Updated Registration of Media Type EVRC . . . . . . . . . <a href="#page-13">13</a>
74 <a href="#section-6.6">6.6</a>. Updated Registration of Media Type EVRC0 . . . . . . . . . <a href="#page-15">15</a>
75 <a href="#section-6.7">6.7</a>. Mapping MIME Parameters into SDP . . . . . . . . . . . . . <a href="#page-17">17</a>
76 <a href="#section-6.8">6.8</a>. Usage in Offer/Answer . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
77 <a href="#section-7">7</a>. Backward Compatibility with <a href="./rfc3558">RFC 3558</a> . . . . . . . . . . . . . <a href="#page-19">19</a>
78 <a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
79 <a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
80 <a href="#section-10">10</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
81 <a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
82 <a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
83 <a href="#section-11.2">11.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Xie &amp; Kapoor Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 This document defines support for the header-free and interleaved/
116 bundled packet formats for the EVRC-B codec, a new compact bundled
117 format for the EVRC and EVRC-B codecs, as well as discontinuous
118 transmission (DTX) support for EVRC and EVRC-B-encoded speech
119 transported via RTP. Voice over IP (VoIP) applications operating
120 over low bandwidth dial-up and wireless networks require such EVRC
121 RTP payload capabilities for efficient use of the bandwidth.
122
123 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Support of EVRC-B Codec</span>
124
125 EVRC-B [<a href="#ref-3" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 and 68 for Wideband Spread Spectrum Digital Systems&quot;">3</a>] is an extension to EVRC [<a href="#ref-2" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 for Wideband Spread Spectrum Digital Systems&quot;">2</a>] developed in the Third
126 Generation Partnership Project 2 (3GPP2). EVRC-B [<a href="#ref-3" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 and 68 for Wideband Spread Spectrum Digital Systems&quot;">3</a>] compresses each
127 20 milliseconds of 8000Hz, 16-bit sampled speech input into output
128 frames of one of the four different sizes: Rate 1 (171 bits), Rate
129 1/2 (80 bits), Rate 1/4 (40 bits), or Rate 1/8 (16 bits). In
130 addition, there are two zero-bit codec frame types: null frames and
131 erasure frames, similar to EVRC [<a href="#ref-2" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 for Wideband Spread Spectrum Digital Systems&quot;">2</a>]. One significant enhancement in
132 EVRC-B is the use of 1/4-rate frames that were not used in EVRC.
133 This provides lower average data rates (ADRs) compared to EVRC, for a
134 given voice quality.
135
136 Since speech frames encoded by EVRC-B are different from those
137 encoded by EVRC, EVRC-B and EVRC codecs do not interoperate with each
138 other. At the initiation of an RTP session, the RTP sender and
139 receiver need to indicate (e.g., using MIME subtypes that are
140 separate from those of EVRC) that EVRC-B is to be used for the
141 ensuing session.
142
143 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Compact (Header-free) Bundled Format</span>
144
145 The current interleaved/bundled packet format defined in <a href="./rfc3558">RFC 3558</a>
146 allows bundling of multiple speech frames of different rates in a
147 single RTP packet, sending mode change requests, and interleaving.
148 To support these functions, a Table of Contents (ToC) is used in each
149 RTP packet, in addition to the standard RTP header. The size of the
150 ToC varies depending on the number of EVRC frames carried in the
151 packet [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>].
152
153 The current header-free packet format defined in <a href="./rfc3558">RFC 3558</a> is more
154 compact and optimized for use over wireless links. It eliminates the
155 need for a ToC by requiring that each RTP packet contain only one
156 speech frame (of any allowable rate), i.e., bundling is not allowed.
157 Moreover, interleaving and mode change requests are not supported in
158 the header-free format [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>].
159
160
161
162
163
164 <span class="grey">Xie &amp; Kapoor Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
167
168
169 The compact bundled format described in this document presents the
170 user an alternative to the header-free format defined in <a href="./rfc3558">RFC 3558</a>.
171 This format allows bundling of multiple EVRC or EVRC-B frames without
172 the addition of extra headers, as would be in the case of the
173 interleaved/bundled format. However, in order to use this compact
174 bundled format, only one EVRC/EVRC-B rate (full rate or 1/2 rate) can
175 be used in the session. Similar to the header-free format defined in
176 <a href="./rfc3558">RFC 3558</a>, interleaving and mode change requests are not supported in
177 the compact bundled format.
178
179 <span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Discontinuous Transmission (DTX)</span>
180
181 Information carried in frames of EVRC and EVRC-B codecs varies little
182 during periods of silence. The transmission of these frames across
183 the radio interface in a wireless system is expensive, in terms of
184 capacity; therefore, suppression of these frames is desirable. Such
185 an operation is called DTX, also known as silence suppression.
186
187 In general, when DTX/silence suppression is applied, the first few
188 frames of silence may be transmitted at the beginning of the period
189 of silence to establish background noise. Then, a portion of the
190 stream of subsequent silence frames is not transmitted, and is
191 discarded at the sender. At the receiver, background or comfort
192 noise may be generated by using the previously received silence
193 frames.
194
195 The full detail of DTX/silence suppression operation can be found in
196 DTX [<a href="#ref-8" title="&quot;Discontinuous Transmission (DTX) of Speech in cdma2000 Systems&quot;">8</a>] as well as in <a href="./rfc3551">RFC 3551</a> [<a href="#ref-9" title="&quot;RTP Profile for Audio and Video Conferences with Minimal Control&quot;">9</a>], and in <a href="./rfc3558">RFC 3558</a> [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>]. This
197 document only defines the additional optional MIME parameters
198 (silencesupp, dtxmax, dtxmin, and hangover) for setting up a DTX/
199 silence suppression session, where "silencesupp" is for indicating
200 the capability and willingness of using DTX/silence suppression;
201 "dtxmax" and "dtxmin", for indicating the desired range of DTX update
202 interval; and "hangover", for indicating the desired number of
203 silence frames at the beginning of each silence period to establish
204 background noise at the receiver (see <a href="#section-6.1">Section 6.1</a> for detailed
205 definition).
206
207 The EVRC and EVRC-B codecs, in variable-rate operation mode, send
208 1/8-rate frames during periods of silence, while in single-rate
209 operation mode (see <a href="#section-4">Section 4</a>), silence is encoded and sent in frames
210 of the same rate as that of speech frames. The DTX parameters
211 defined in this document apply to 1/8-rate frames in the variable-
212 rate mode and to silence frames in the single-rate operation mode.
213
214 For simplicity, in the rest of this document the term "silence frame"
215 refers either to an 1/8-rate frame in variable-rate operation or a
216 frame that contains only silence in the signal-rate operation.
217
218
219
220 <span class="grey">Xie &amp; Kapoor Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
223
224
225 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions</span>
226
227 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
228 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
229 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-1" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">1</a>].
230
231 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. EVRC-B Codec</span>
232
233 Three RTP packet formats are supported for the EVRC-B codec: the
234 interleaved/bundled packet format, the header-free packet format, and
235 the compact bundled packet format. For the interleaved/bundled and
236 header-free packet formats, the operational details and capabilities,
237 such as ToC, interleaving, and bundling, of EVRC-B, are exactly the
238 same as those of EVRC, as defined in <a href="./rfc3558">RFC 3558</a> [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>], except that the
239 mode change request field in the ToC MUST be interpreted according to
240 the definition of the RATE_REDUC parameter in EVRC-B [<a href="#ref-3" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 and 68 for Wideband Spread Spectrum Digital Systems&quot;">3</a>]. The
241 compact bundled packet format for EVRC-B is defined in <a href="#section-4">Section 4</a> of
242 this document.
243
244 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Compact Bundled Format</span>
245
246 A packet in the compact bundled format consists of an RTP header,
247 followed by a sequence of one or more consecutive EVRC/EVRC-B codec
248 data frames of the same rate, as shown below:
249
250 0 1 2 3
251 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
253 | RTP Header [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>] |
254 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
255 | |
256 | One or more EVRC/EVRC-B data frames of same rate |
257 | .... |
258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
259
260 The codec data frames MUST be generated from the output of the codec
261 following the procedure described in <a href="./rfc3558#section-5.2">Section&nbsp;5.2 in RFC 3558</a> [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>], and
262 all MUST be of the same rate and size.
263
264 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Single-Rate Operation</span>
265
266 As mentioned earlier, in order to use the compact bundled format, all
267 the EVRC/EVRC-B data frames in the session MUST be of the same rate.
268 This packet format may carry only full or half-rate frames.
269
270
271
272
273
274
275
276 <span class="grey">Xie &amp; Kapoor Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
279
280
281 For a session that uses the compact bundled format, the rate for the
282 session can be determined during the session setup signaling, for
283 example, via Session Description Protocol (SDP) exchanges. See
284 <a href="#section-6">Section 6</a> below for more details.
285
286 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Storage Format for EVRC-B Codec</span>
287
288 The storage format is used for storing EVRC-B-encoded speech frames,
289 e.g., as a file or e-mail attachment.
290
291 The file begins with a magic number to identify the vocoder that is
292 used. The magic number for EVRC-B corresponds to the ASCII character
293 string:
294
295 "#!EVRC-B\n"
296 (or 0x2321 0x4556 0x5243 0x2d42 0x0a in hexadecimal).
297
298 Note that the "\n" is an important part of both this magic number and
299 the "#!EVRC\n" magic number defined in <a href="./rfc3558#section-11">Section&nbsp;11 of RFC 3558</a>, and
300 the "\n" MUST be included in any comparison of either magic number,
301 since, otherwise, a prefix of the EVRC-B magic number could be
302 mistaken for the EVRC magic number.
303
304 The codec data frames are stored in consecutive order, with a single
305 ToC entry field, extended to one octet, prefixing each codec data
306 frame. The ToC field, as defined in Section 5.1 of [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>], is extended
307 to one octet by setting the four most significant bits of the octet
308 to zero. For example, a ToC value of 4 (a full-rate frame) is stored
309 as 0x04.
310
311 Speech frames lost in transmission and non-received frames MUST be
312 stored as erasure frames to maintain synchronization with the
313 original media.
314
315 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Media Type Definitions</span>
316
317 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Registration of Media Type EVRC1</span>
318
319 Type name: audio
320
321 Subtype names: EVRC1
322
323 Required parameters: none
324
325
326
327
328
329
330
331
332 <span class="grey">Xie &amp; Kapoor Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
335
336
337 Optional parameters:
338
339 ptime: See <a href="./rfc4566">RFC 4566</a> [<a href="#ref-7" title="&quot;SDP: Session Description Protocol&quot;">7</a>].
340
341 maxptime: The maximum amount of media that can be encapsulated in
342 each packet, expressed as time in milliseconds. The time MUST
343 be calculated as the sum of the time the media present in the
344 packet represents. The time SHOULD be a multiple of the
345 duration of a single codec data frame (20 msec). If not
346 signaled, the default maxptime value MUST be 200 milliseconds.
347
348 fixedrate: Indicates the EVRC rate of the session while in
349 single-rate operation. Valid values include: 0.5 and 1, where
350 a value of 0.5 indicates the 1/2 rate, while a value of 1
351 indicates the full rate. If this parameter is not present, 1/2
352 rate is assumed.
353
354 silencesupp: Permissible values are 0 and 1. A value of 1
355 indicates that the sender of this parameter: a) is capable of
356 receiving silence-suppressed speech using DTX, AND b) is
357 capable of and will send out silence-suppressed speech using
358 DTX, unless the other end indicates that it does not want to
359 receive silence-suppressed speech using DTX.
360
361 A value of 0 indicates that the sender of this parameter: a)
362 does NOT want to receive silence-suppressed speech using DTX,
363 AND b) will NOT send out silence-suppressed speech using DTX.
364
365 If this parameter is not present, the default value 1 MUST be
366 assumed. If the RTP receiver indicates through the use of SIP
367 signaling or other means that it is incapable of or unwilling
368 to use silence suppression using DTX, silence suppression using
369 DTX as specified in this document MUST NOT be used for the
370 session.
371
372 dtxmax: Permissible values are from 0 to 255. Indicates the
373 maximum DTX update interval in number of frames. During DTX,
374 the RTP sender occasionally updates the RTP receiver about the
375 change in background noise characteristics, etc., by sending a
376 new silence frame to the RTP receiver. The RTP receiver may
377 use 'dtxmax' to indicate to the RTP sender the maximum interval
378 (in number of frames) between any two DTX updates it expects to
379 receive from the RTP sender.
380
381 If this parameter is not present in a session that uses DTX,
382 the default value 32, as specified in [<a href="#ref-8" title="&quot;Discontinuous Transmission (DTX) of Speech in cdma2000 Systems&quot;">8</a>], MUST be assumed.
383 This parameter MUST be ignored if silence suppression using DTX
384 is not used for the session.
385
386
387
388 <span class="grey">Xie &amp; Kapoor Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
391
392
393 Note also that if the RTP receiver elects to detect DTX using
394 dtxmax, the dtxmax parameter will affect the amount of delay
395 the RTP receiver sees before detecting DTX in the stream.
396
397 dtxmin: Permissible values are from 0 to 255. Indicates the
398 minimum DTX update interval in number of frames. The RTP
399 receiver may use 'dtxmin' to indicate to the RTP sender the
400 minimal interval (in number of frames) between any two DTX
401 updates it expects to receive from the RTP sender.
402
403 If this parameter is not present, the default value 12, as
404 specified in [<a href="#ref-8" title="&quot;Discontinuous Transmission (DTX) of Speech in cdma2000 Systems&quot;">8</a>] MUST be assumed. This parameter MUST be
405 ignored if silence suppression using DTX is not used for the
406 session.
407
408 hangover: Permissible values are from 0 to 255. Indicates the
409 number of consecutive silence frames transmitted at the end of
410 an active speech interval but before the DTX interval begins.
411 When setting up an RTP session that uses DTX, an RTP receiver
412 can use this parameter to signal the number of silence frames
413 it expects to receive before the beginning of DTX. While
414 hangover=0 is allowed, it is RECOMMENDED that hangover be set
415 to 1 or greater since the presence of silence frames at the end
416 of an active speech can help the RTP receiver to identify the
417 beginning of the DTX period.
418
419 If this parameter is not present for a session that uses DTX,
420 the default value 1, as specified in [<a href="#ref-8" title="&quot;Discontinuous Transmission (DTX) of Speech in cdma2000 Systems&quot;">8</a>] MUST be assumed. This
421 parameter MUST be ignored if silence suppression using DTX is
422 not used for the session.
423
424 Encoding considerations:
425 This media type is framed binary data (see <a href="./rfc4288#section-4.8">RFC 4288, Section&nbsp;4.8</a>)
426 and is defined for transfer of EVRC-encoded data via RTP, using
427 the compact bundled format as described in <a href="./rfc4788">RFC 4788</a>.
428
429 Security considerations: See <a href="./rfc4788#section-9">Section&nbsp;9 of RFC 4788</a>.
430
431 Interoperability considerations: none
432
433 Published specification:
434 The EVRC vocoder is specified in 3GPP2 C.S0014 [<a href="#ref-2" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 for Wideband Spread Spectrum Digital Systems&quot;">2</a>]. Transfer
435 method with compact bundled RTP format is specified in <a href="./rfc4788">RFC 4788</a>.
436
437 Applications that use this media type:
438 It is expected that many VoIP applications (as well as mobile
439 applications) will use this type.
440
441
442
443
444 <span class="grey">Xie &amp; Kapoor Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
447
448
449 Additional information: none
450
451 Person &amp; email address to contact for further information:
452 Qiaobing Xie &lt;[email protected]&gt;
453
454 Intended usage: COMMON
455
456 Restrictions on usage:
457 This media type depends on RTP framing; hence, it is only defined
458 for transfer via RTP (<a href="./rfc3550">RFC 3550</a> [<a href="#ref-5" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">5</a>]). Transfer within other
459 framing protocols is not defined at this time.
460
461 Author:
462 Qiaobing Xie
463
464 Change controller:
465 IETF Audio/Video Transport working group delegated from the IESG.
466
467 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Registration of Media Type EVRCB</span>
468
469 Type name: audio
470
471 Subtype names: EVRCB
472
473 Required parameters: none
474
475 Optional parameters:
476
477 ptime: see <a href="./rfc4566">RFC 4566</a> [<a href="#ref-7" title="&quot;SDP: Session Description Protocol&quot;">7</a>].
478
479 maxptime: The maximum amount of media that can be encapsulated in
480 each packet, expressed as time in milliseconds. The time MUST
481 be calculated as the sum of the time the media present in the
482 packet represents. The time SHOULD be a multiple of the
483 duration of a single codec data frame (20 msec). If not
484 signaled, the default maxptime value MUST be 200 milliseconds.
485
486 maxinterleave: Maximum number for interleaving length (field LLL
487 in the Interleaving Octet). The interleaving lengths used in
488 the entire session MUST NOT exceed this maximum value. If not
489 signaled, the maxinterleave length MUST be 5.
490
491 silencesupp: see <a href="#section-6.1">Section 6.1</a> for definition. If this parameter
492 is not present, the default value 1 MUST be assumed.
493
494
495
496
497
498
499
500 <span class="grey">Xie &amp; Kapoor Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
503
504
505 dtxmax: see <a href="#section-6.1">Section 6.1</a>
506
507 dtxmin: see <a href="#section-6.1">Section 6.1</a>
508
509 hangover: see <a href="#section-6.1">Section 6.1</a>
510
511 Encoding considerations:
512 This media type is framed binary data (see <a href="./rfc4288#section-4.8">RFC 4288, Section&nbsp;4.8</a>)
513 and is defined for transfer of EVRC-B-encoded data via RTP using
514 the Interleaved/Bundled packet format specified in <a href="./rfc3558">RFC 3558</a> [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>].
515
516 Security considerations: See <a href="./rfc4788#section-9">Section&nbsp;9 of RFC 4788</a>.
517
518 Interoperability considerations: none
519
520 Published specification:
521 The EVRC-B vocoder is specified in 3GPP2 C.S0014-B [<a href="#ref-3" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 and 68 for Wideband Spread Spectrum Digital Systems&quot;">3</a>]. Transfer
522 method with Interleaved/Bundled packet format via RTP is specified
523 in <a href="./rfc3558">RFC 3558</a>.
524
525 Applications that use this media type:
526 It is expected that many VoIP applications (as well as mobile
527 applications) will use this type.
528
529 Additional information:
530 The following information applies for storage format only.
531
532 Magic number: #!EVRC-B\n (see <a href="./rfc4788#section-5">Section&nbsp;5 of RFC 4788</a>)
533 File extensions: evb, EVB
534 Macintosh file type code: None
535 Object identifier or OID: None
536
537 Person &amp; email address to contact for further information:
538 Qiaobing Xie &lt;[email protected]&gt;
539
540 Intended usage: COMMON
541
542 Restrictions on usage:
543 This media type may be used with RTP framing (<a href="./rfc3550">RFC 3550</a> [<a href="#ref-5" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">5</a>]) and as
544 a storage format. When used with RTP, the procedures in <a href="#section-3">Section 3</a>
545 MUST be followed. In all other contexts, the storage format
546 defined in <a href="#section-5">Section 5</a> MUST be used.
547
548 Author:
549 Qiaobing Xie
550
551
552
553
554
555
556 <span class="grey">Xie &amp; Kapoor Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
559
560
561 Change controller:
562 IETF Audio/Video Transport working group delegated from the IESG.
563
564 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Registration of Media Type EVRCB0</span>
565
566 Type name: audio
567
568 Subtype names: EVRCB0
569
570 Required parameters: none
571
572 Optional parameters:
573
574 silencesupp: see <a href="#section-6.1">Section 6.1</a> for definition. If this parameter
575 is not present, the default value 1 MUST be assumed.
576
577 dtxmax: see <a href="#section-6.1">Section 6.1</a>
578
579 dtxmin: see <a href="#section-6.1">Section 6.1</a>
580
581 hangover: see <a href="#section-6.1">Section 6.1</a>
582
583 Encoding considerations:
584 This media type is framed binary data (see <a href="./rfc4288#section-4.8">RFC 4288, Section&nbsp;4.8</a>)
585 and is defined for transfer of EVRC-B-encoded data via RTP using
586 the Header-Free packet format specified in <a href="./rfc3558">RFC 3558</a> [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>].
587
588 Security considerations: See <a href="./rfc4788#section-9">Section&nbsp;9 of RFC 4788</a>.
589
590 Interoperability considerations: none
591
592 Published specification:
593 The EVRC-B vocoder is specified in 3GPP2 C.S0014-B [<a href="#ref-3" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 and 68 for Wideband Spread Spectrum Digital Systems&quot;">3</a>]. Transfer
594 method with Header-Free packet format via RTP is specified in <a href="./rfc3558">RFC</a>
595 <a href="./rfc3558">3558</a> and <a href="./rfc4788">RFC 4788</a>.
596
597 Applications that use this media type:
598 It is expected that many VoIP applications (as well as mobile
599 applications) will use this type.
600
601 Additional information: none
602
603 Person &amp; email address to contact for further information:
604 Qiaobing Xie &lt;[email protected]&gt;
605
606
607
608
609
610
611
612 <span class="grey">Xie &amp; Kapoor Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
615
616
617 Intended usage: COMMON
618
619 Restrictions on usage:
620 This media type depends on RTP framing; hence, it is only defined
621 for transfer via RTP (<a href="./rfc3550">RFC 3550</a> [<a href="#ref-5" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">5</a>]). Transfer within other
622 framing protocols is not defined at this time.
623
624 Author:
625 Qiaobing Xie
626
627 Change controller:
628 IETF Audio/Video Transport working group delegated from the IESG.
629
630 <span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Registration of Media Type EVRCB1</span>
631
632 Type name: audio
633
634 Subtype names: EVRCB1
635
636 Required parameters: none
637
638 Optional parameters:
639
640 ptime: see <a href="./rfc4566">RFC 4566</a> [<a href="#ref-7" title="&quot;SDP: Session Description Protocol&quot;">7</a>].
641
642 maxptime: The maximum amount of media that can be encapsulated in
643 each packet, expressed as time in milliseconds. The time MUST
644 be calculated as the sum of the time the media present in the
645 packet represents. The time SHOULD be a multiple of the
646 duration of a single codec data frame (20 msec). If not
647 signaled, the default maxptime value MUST be 200 milliseconds.
648
649 fixedrate: Indicates the EVRC-B rate of the session while in
650 single-rate operation. Valid values include: 0.5 and 1, where
651 a value of 0.5 indicates the 1/2 rate while a value of 1
652 indicates the full rate. If this parameter is not present, 1/2
653 rate is assumed.
654
655 silencesupp: see <a href="#section-6.1">Section 6.1</a> for definition. If this parameter
656 is not present, the default value 1 MUST be assumed.
657
658 dtxmax: see <a href="#section-6.1">Section 6.1</a>
659
660 dtxmin: see <a href="#section-6.1">Section 6.1</a>
661
662
663
664
665
666
667
668 <span class="grey">Xie &amp; Kapoor Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
671
672
673 hangover: see <a href="#section-6.1">Section 6.1</a>
674
675 Encoding considerations:
676 This media type is framed binary data (see <a href="./rfc4288#section-4.8">RFC 4288, Section&nbsp;4.8</a>)
677 and is defined for transfer of EVRC-B-encoded data via RTP using
678 the compact bundled format as described in <a href="./rfc4788">RFC 4788</a>.
679
680 Security considerations: See <a href="./rfc4788#section-9">Section&nbsp;9 of RFC 4788</a>.
681
682 Interoperability considerations: none.
683
684 Published specification:
685 The EVRC-B vocoder is specified in 3GPP2 C.S0014-B [<a href="#ref-3" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 and 68 for Wideband Spread Spectrum Digital Systems&quot;">3</a>]. Transfer
686 method with compact bundled RTP format is specified in <a href="./rfc4788">RFC 4788</a>.
687
688 Applications that use this media type:
689 It is expected that many VoIP applications (as well as mobile
690 applications) will use this type.
691
692 Additional information: none
693
694 Person &amp; email address to contact for further information:
695 Qiaobing Xie &lt;[email protected]&gt;
696
697 Intended usage: COMMON
698
699 Restrictions on usage:
700 This media type depends on RTP framing; hence, it is only defined
701 for transfer via RTP (<a href="./rfc3550">RFC 3550</a> [<a href="#ref-5" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">5</a>]). Transfer within other
702 framing protocols is not defined at this time.
703
704 Author:
705 Qiaobing Xie
706
707 Change controller:
708 IETF Audio/Video Transport working group delegated from the IESG.
709
710 <span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Updated Registration of Media Type EVRC</span>
711
712 (The definition is from <a href="./rfc3558">RFC 3558</a>, added with the optional DTX
713 parameters, and updated with the new template specified in [<a href="#ref-10" title="&quot;Media Type Registration of RTP Payload Formats&quot;">10</a>].)
714
715 Type name: audio
716
717 Subtype names: EVRC
718
719
720
721
722
723
724 <span class="grey">Xie &amp; Kapoor Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
727
728
729 Required parameters: none
730
731 Optional parameters:
732
733 ptime: Defined as usual for RTP audio (see <a href="./rfc4566">RFC 4566</a>).
734
735 maxptime: The maximum amount of media that can be encapsulated in
736 each packet, expressed as time in milliseconds. The time SHALL
737 be calculated as the sum of the time the media present in the
738 packet represents. The time SHOULD be a multiple of the
739 duration of a single codec data frame (20 msec). If not
740 signaled, the default maxptime value SHALL be 200 milliseconds.
741
742 maxinterleave: Maximum number for interleaving length (field LLL
743 in the Interleaving Octet). The interleaving lengths used in
744 the entire session MUST NOT exceed this maximum value. If not
745 signaled, the maxinterleave length SHALL be 5.
746
747 silencesupp: see <a href="#section-6.1">Section 6.1</a> for definition. If this parameter
748 is not present, the default value 1 MUST be assumed.
749
750 dtxmax: see <a href="#section-6.1">Section 6.1</a>
751
752 dtxmin: see <a href="#section-6.1">Section 6.1</a>
753
754 hangover: see <a href="#section-6.1">Section 6.1</a>
755
756 Encoding considerations:
757 This media type is framed binary data (see <a href="./rfc4288#section-4.8">RFC 4288, Section&nbsp;4.8</a>),
758 and is defined for transfer of EVRC-encoded data via RTP using the
759 Interleaved/Bundled packet format specified in Sections <a href="#section-4.1">4.1</a>, <a href="#section-6">6</a>,
760 and 7 of <a href="./rfc3558">RFC 3558</a>. It is also defined for other transfer methods
761 using the storage format specified in <a href="./rfc3558#section-11">Section&nbsp;11 of RFC 3558</a>.
762
763 Security considerations: See <a href="#section-14">Section 14</a>, "Security Considerations",
764 of <a href="./rfc3558">RFC 3558</a>.
765
766 Interoperability considerations:
767 The DTX parameters are receiver options. Existing <a href="./rfc3558">RFC 3558</a>
768 implementations will not send any of the DTX parameters in their
769 SDP and will ignore any DTX parameters they receive. The adaptive
770 DTX behavior of DTX-capable EVRC codecs (as detailed in [<a href="#ref-8" title="&quot;Discontinuous Transmission (DTX) of Speech in cdma2000 Systems&quot;">8</a>],
771 Section 4.3.5) ensures interoperability with non-DTX EVRC codecs.
772
773 Published specification:
774 The EVRC vocoder is specified in 3GPP2 C.S0014 [<a href="#ref-2" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 for Wideband Spread Spectrum Digital Systems&quot;">2</a>]. Transfer
775 methods are specified in <a href="./rfc3558">RFC 3558</a>.
776
777
778
779
780 <span class="grey">Xie &amp; Kapoor Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
783
784
785 Applications that use this media type:
786 It is expected that many VoIP applications (as well as mobile
787 applications) will use this type.
788
789 Additional information:
790 The following information applies for storage format only.
791
792 Magic number: #!EVRC\n (see <a href="./rfc3558#section-11">Section&nbsp;11 of RFC 3558</a>)
793 File extensions: evc, EVC
794 Macintosh file type code: none
795 Object identifier or OID: none
796
797 Person &amp; email address to contact for further information:
798 Qiaobing Xie &lt;[email protected]&gt;
799
800 Intended usage: COMMON
801
802 Restrictions on usage:
803 This media type may be used with RTP framing (<a href="./rfc3550">RFC 3550</a> [<a href="#ref-5" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">5</a>]) and as
804 a storage format. When used with RTP, the procedures in <a href="./rfc3558#section-4.1">RFC 3558,
805 Section&nbsp;4.1</a>, MUST be followed. In all other contexts, the storage
806 format defined in <a href="./rfc3558#section-11">RFC 3558, Section&nbsp;11</a>, MUST be used.
807
808 Author:
809 Adam Li/Qiaobing Xie
810
811 Change controller:
812 IETF Audio/Video Transport working group delegated from the IESG.
813
814 <span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. Updated Registration of Media Type EVRC0</span>
815
816 (The definition is from <a href="./rfc3558">RFC 3558</a>, added with the optional DTX
817 parameters, and updated with the new template specified in [<a href="#ref-10" title="&quot;Media Type Registration of RTP Payload Formats&quot;">10</a>].)
818
819 Type name: audio
820
821 Subtype names: EVRC0
822
823 Required parameters: none
824
825 Optional parameters:
826
827 silencesupp: see <a href="#section-6.1">Section 6.1</a> for definition. If this parameter
828 is not present, the default value 1 MUST be assumed.
829
830
831
832
833
834
835
836 <span class="grey">Xie &amp; Kapoor Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
839
840
841 dtxmax: see <a href="#section-6.1">Section 6.1</a>
842
843 dtxmin: see <a href="#section-6.1">Section 6.1</a>
844
845 hangover: see <a href="#section-6.1">Section 6.1</a>
846
847 Encoding considerations:
848 This media type is framed binary data (see <a href="./rfc4288#section-4.8">RFC 4288, Section&nbsp;4.8</a>)
849 and is only defined for transfer of EVRC-encoded data via RTP
850 using the Header-Free packet format specified in <a href="./rfc3558#section-4.2">Section&nbsp;4.2 of
851 RFC 3558</a>.
852
853 Security considerations: See <a href="#section-14">Section 14</a>, "Security Considerations",
854 of <a href="./rfc3558">RFC 3558</a>.
855
856 Interoperability considerations:
857 The DTX parameters are receiver options. Existing <a href="./rfc3558">RFC 3558</a>
858 implementations will not send any of the DTX parameters in their
859 SDP and will ignore any DTX parameters they receive. The adaptive
860 DTX behavior of DTX-capable EVRC codecs (as detailed in [<a href="#ref-8" title="&quot;Discontinuous Transmission (DTX) of Speech in cdma2000 Systems&quot;">8</a>],
861 Section 4.3.5) ensures interoperability with non-DTX EVRC codecs.
862
863 Published specification:
864 The EVRC vocoder is specified in 3GPP2 C.S0014 [<a href="#ref-2" title="&quot;Enhanced Variable Rate Codec, Speech Service Option 3 for Wideband Spread Spectrum Digital Systems&quot;">2</a>]. Transfer
865 methods are specified in <a href="./rfc3558">RFC 3558</a>.
866
867 Applications that use this media type:
868 It is expected that many VoIP applications (as well as mobile
869 applications) will use this type.
870
871 Additional information: none
872
873 Person &amp; email address to contact for further information:
874 Qiaobing Xie &lt;[email protected]&gt;
875
876 Intended usage: COMMON
877
878 Restrictions on usage:
879 This media type depends on RTP framing; hence, it is only defined
880 for transfer via RTP (<a href="./rfc3550">RFC 3550</a> [<a href="#ref-5" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">5</a>]). Transfer within other
881 framing protocols is not defined at this time.
882
883 Author:
884 Adam Li/Qiaobing Xie
885
886
887
888
889
890
891
892 <span class="grey">Xie &amp; Kapoor Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
895
896
897 Change controller:
898 IETF Audio/Video Transport working group delegated from the IESG.
899
900 <span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. Mapping MIME Parameters into SDP</span>
901
902 The information carried in the MIME media type specification has a
903 specific mapping to fields in the Session Description Protocol (SDP)
904 [<a href="#ref-7" title="&quot;SDP: Session Description Protocol&quot;">7</a>], which is commonly used to describe RTP sessions. When SDP is
905 used to specify sessions employing the compact bundled format for
906 EVRC/EVRC-B-encoded speech, the mapping is as follows:
907
908 o The MIME type ("audio") goes in SDP "m=" as the media name.
909
910 o The MIME subtype ("EVRC", "EVRC0", "EVRC1", "EVRCB", EVRCB0", or
911 "EVRCB1") goes in SDP "a=rtpmap" as the encoding name.
912
913 o The optional parameters "ptime" and "maxptime" (for subtypes EVRC,
914 EVRC1, EVRCB, and EVRCB1) go in the SDP "a=ptime" and "a=maxptime"
915 attributes, respectively.
916
917 o The optional parameter "maxinterleave" (for subtypes EVRC and
918 EVRCB) goes in the SDP "a=fmtp" attribute by copying it directly
919 from the MIME media type string as "maxinterleave=value".
920
921 o The optional parameter "fixedrate" (for subtypes EVRC1 and EVRCB1)
922 goes in the "a=fmtp" attribute by copying it directly from the
923 MIME media type string as "fixedrate=value".
924
925 o The optional parameters "silencesupp", "dtxmax", "dtxmin", and
926 "hangover" go in the "a=fmtp" attribute by copying it directly
927 from the MIME media type string as "silencesupp=value",
928 "dtxmax=value", "dtxmin=value", and "hangover=value",
929 respectively.
930
931 Example of usage of EVRC1:
932
933 m=audio 49120 RTP/AVP 97
934 a=rtpmap:97 EVRC1/8000
935 a=fmtp:97 fixedrate=0.5
936 a=maxptime:120
937
938 Example of usage of EVRCB:
939
940 m=audio 49120 RTP/AVP 97
941 a=rtpmap:97 EVRCB/8000
942 a=maxptime:120
943
944
945
946
947
948 <span class="grey">Xie &amp; Kapoor Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
951
952
953 Example of usage of EVRCB0:
954
955 m=audio 49120 RTP/AVP 97
956 a=rtpmap:97 EVRCB0/8000
957
958 Example of usage of EVRCB1:
959
960 m=audio 49120 RTP/AVP 97
961 a=rtpmap:97 EVRCB1/8000
962 a=fmtp:97 fixedrate=0.5
963 a=maxptime:100
964
965 Example of usage of EVRC with DTX with silencesupp=1:
966
967 m=audio 49120 RTP/AVP 97
968 a=rtpmap:97 EVRC/8000
969 a=fmtp:97 silencesupp=1 dtxmax=32 dtxmin=12 hangover=1
970
971 Example of usage of EVRC with DTX with silencesupp=0:
972
973 m=audio 49120 RTP/AVP 97
974 a=rtpmap:97 EVRC/8000
975 a=fmtp:97 silencesupp=0
976
977 <span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a>. Usage in Offer/Answer</span>
978
979 All SDP parameters in this payload format are declarative, and all
980 reasonable values are expected to be supported. In particular, when
981 DTX is supported, the RTP sender implementation SHOULD support
982 hangover, dtxmin, and dtxmax values from 0 to 255. Thus, the
983 standard usage of Offer/Answer, as described in <a href="./rfc3264">RFC 3264</a> [<a href="#ref-6" title="&quot;An Offer/Answer Model with the Session Description Protocol (SDP)&quot;">6</a>], SHOULD
984 be followed.
985
986 In addition, the following rules MUST be followed while negotiating
987 DTX parameters:
988
989 1. If any DTX parameter is not present in either offer and/or
990 answer, the default value of the DTX parameter MUST be assumed.
991
992 2. If silencesupp is present and set to 0 in either offer or answer,
993 the values of all received DTX parameters other than silencesupp
994 SHOULD be ignored.
995
996 3. In an offer or answer, the value of dtxmax SHOULD always be
997 larger than or equal to the value of dtxmin, regardless of
998 whether the values are indicated explicitly or implicitly by
999 default. Moreover, if the indicated value of dtxmin is larger
1000
1001
1002
1003
1004 <span class="grey">Xie &amp; Kapoor Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
1007
1008
1009 than that of dtxmax, an RTP sender MUST ignore the indicated
1010 values and MUST fall back on using the default dtxmin and dtxmax
1011 values.
1012
1013 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Backward Compatibility with <a href="./rfc3558">RFC 3558</a></span>
1014
1015 This document adds new optional DTX parameters to the original EVRC
1016 payload subtypes "EVRC" and "EVRC0" defined in <a href="./rfc3558">RFC 3558</a>. Since the
1017 new DTX parameters are receiver options, we expect that the existing
1018 <a href="./rfc3558">RFC 3558</a> implementations will not send any of the DTX parameters in
1019 their SDP and will ignore any DTX parameters they receive. The
1020 adaptive DTX behavior of DTX-capable EVRC codecs (as detailed in [<a href="#ref-8" title="&quot;Discontinuous Transmission (DTX) of Speech in cdma2000 Systems&quot;">8</a>],
1021 Section 4.3.5) ensures the backward interoperability between the DTX-
1022 capable EVRC codec and non-DTX EVRC codecs.
1023
1024 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
1025
1026 Four (4) new MIME subtype registrations - "EVRC1", "EVRCB", "EVRCB0",
1027 and "EVRCB1" - are defined in this document (see <a href="#section-6.1">Section 6.1</a> -
1028 <a href="#section-6.4">Section 6.4</a>) for EVRC-B and compact bundled payload format support.
1029
1030 For all the EVRC and EVRC-B RTP payload formats defined in <a href="./rfc3558">RFC 3558</a>
1031 [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>] and <a href="./rfc4788">RFC 4788</a>, four additional optional parameters -
1032 "silencesupp", "dtxmax", "dtxmin", and "hangover" - are defined and
1033 used in DTX.
1034
1035 The MIME subtype registrations "EVRC" and "EVRC0", originally defined
1036 in <a href="./rfc3558">RFC 3558</a> [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>], are updated with the optional DTX parameters (see
1037 Sections <a href="#section-6.5">6.5</a> and <a href="#section-6.6">6.6</a>).
1038
1039 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
1040
1041 Implementations using the payload defined in this specification are
1042 subject to the security considerations discussed in <a href="./rfc3558">RFC 3558</a> [<a href="#ref-4" title="&quot;RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)&quot;">4</a>], <a href="./rfc3550">RFC</a>
1043 <a href="./rfc3550">3550</a> [<a href="#ref-5" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">5</a>], and any appropriate profile (for example, <a href="./rfc3551">RFC 3551</a> [<a href="#ref-9" title="&quot;RTP Profile for Audio and Video Conferences with Minimal Control&quot;">9</a>]).
1044 This payload does not specify any different security services.
1045
1046 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgements</span>
1047
1048 The following people have made significant contributions to this
1049 document (in alphabetical order): Parag Agashe, Jim Ashley,
1050 Harikishan Desineni, Serafin Diaz, Harinath Garudadri, Gouri
1051 Johanssen, Ananth Kandhadai, Waqar Mohsin, Ashok Roy, Gino Scribano,
1052 and Gajinder Singh Vij.
1053
1054 Special thanks to Colin Perkins, Magnus Westerlund, and Adam Li for
1055 their careful review and comments that significantly improved the
1056 quality of this document.
1057
1058
1059
1060 <span class="grey">Xie &amp; Kapoor Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
1063
1064
1065 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
1066
1067 <span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
1068
1069 [<a id="ref-1">1</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
1070 Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
1071
1072 [<a id="ref-2">2</a>] "Enhanced Variable Rate Codec, Speech Service Option 3 for
1073 Wideband Spread Spectrum Digital Systems", 3GPP2 C.S0014,
1074 January 1997.
1075
1076 [<a id="ref-3">3</a>] "Enhanced Variable Rate Codec, Speech Service Option 3 and 68
1077 for Wideband Spread Spectrum Digital Systems", 3GPP2 C.S0014-B
1078 v1.0, May 2006.
1079
1080 [<a id="ref-4">4</a>] Li, A., "RTP Payload Format for Enhanced Variable Rate Codecs
1081 (EVRC) and Selectable Mode Vocoders (SMV)", <a href="./rfc3558">RFC 3558</a>,
1082 July 2003.
1083
1084 [<a id="ref-5">5</a>] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
1085 "RTP: A Transport Protocol for Real-Time Applications",
1086 <a href="./rfc3550">RFC 3550</a>, July 2003.
1087
1088 [<a id="ref-6">6</a>] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
1089 the Session Description Protocol (SDP)", <a href="./rfc3264">RFC 3264</a>, June 2002.
1090
1091 [<a id="ref-7">7</a>] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
1092 Description Protocol", <a href="./rfc4566">RFC 4566</a>, July 2006.
1093
1094 [<a id="ref-8">8</a>] "Discontinuous Transmission (DTX) of Speech in cdma2000
1095 Systems", 3GPP2 C.S0076-0, Version 1.0, December 2005.
1096
1097 <span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
1098
1099 [<a id="ref-9">9</a>] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video
1100 Conferences with Minimal Control", <a href="./rfc3551">RFC 3551</a>, July 2003.
1101
1102 [<a id="ref-10">10</a>] Casner, S., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22Media+Type+Registration+of+RTP+Payload+Formats%22'>"Media Type Registration of RTP Payload Formats"</a>,
1103 Work in Progress, March 2006.
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Xie &amp; Kapoor Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
1119
1120
1121 Authors' Addresses
1122
1123 Qiaobing Xie
1124 Motorola, Inc.
1125 1501 W. Shure Drive, 2-F9
1126 Arlington Heights, IL 60004
1127 US
1128
1129 Phone: +1-847-632-3028
1130 EMail: [email protected]
1131
1132
1133 Rohit Kapoor
1134 Qualcomm Inc.
1135 US
1136
1137 Phone: +1-858-845-1161
1138 EMail: [email protected]
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Xie &amp; Kapoor Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc4788">RFC 4788</a> EVRC RTP Format Enhancements January 2007</span>
1175
1176
1177 Full Copyright Statement
1178
1179 Copyright (C) The IETF Trust (2007).
1180
1181 This document is subject to the rights, licenses and restrictions
1182 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
1183 retain all their rights.
1184
1185 This document and the information contained herein are provided on an
1186 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1187 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST,
1188 AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
1189 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
1190 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
1191 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
1192 PURPOSE.
1193
1194 Intellectual Property
1195
1196 The IETF takes no position regarding the validity or scope of any
1197 Intellectual Property Rights or other rights that might be claimed to
1198 pertain to the implementation or use of the technology described in
1199 this document or the extent to which any license under such rights
1200 might or might not be available; nor does it represent that it has
1201 made any independent effort to identify any such rights. Information
1202 on the procedures with respect to rights in RFC documents can be
1203 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
1204
1205 Copies of IPR disclosures made to the IETF Secretariat and any
1206 assurances of licenses to be made available, or the result of an
1207 attempt made to obtain a general license or permission for the use of
1208 such proprietary rights by implementers or users of this
1209 specification can be obtained from the IETF on-line IPR repository at
1210 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
1211
1212 The IETF invites any interested party to bring to its attention any
1213 copyrights, patents or patent applications, or other proprietary
1214 rights that may cover technology that may be required to implement
1215 this standard. Please address the information to the IETF at
1216 [email protected].
1217
1218 Acknowledgement
1219
1220 Funding for the RFC Editor function is currently provided by the
1221 Internet Society.
1222
1223
1224
1225
1226
1227
1228 Xie &amp; Kapoor Standards Track [Page 22]
1229 </pre>