1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Network Working Group R. Kreuter
Request for Comments: 4040 Siemens AG
Category: Standards Track April 2005
<span class="h1">RTP Payload Format for a 64 kbit/s Transparent Call</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document describes how to carry 64 kbit/s channel data
transparently in RTP packets, using a pseudo-codec called
"Clearmode". It also serves as registration for a related MIME type
called "audio/clearmode".
"Clearmode" is a basic feature of VoIP Media Gateways.
Table of Contents
<a href="#section-1">1</a>. Introduction.................................................. <a href="#page-2">2</a>
<a href="#section-2">2</a>. Conventions Used in This Document............................. <a href="#page-2">2</a>
<a href="#section-3">3</a>. 64 kbit/s Data Stream Handling and RTP Header Parameters...... <a href="#page-3">3</a>
<a href="#section-4">4</a>. IANA Considerations........................................... <a href="#page-3">3</a>
<a href="#section-5">5</a>. Mapping to Session Description Protocol (SDP) Parameters...... <a href="#page-5">5</a>
<a href="#section-6">6</a>. Security Considerations....................................... <a href="#page-5">5</a>
<a href="#section-7">7</a>. References.................................................... <a href="#page-6">6</a>
<a href="#section-7.1">7.1</a>. Normative References..................................... <a href="#page-6">6</a>
<a href="#section-7.2">7.2</a>. Informative References................................... <a href="#page-6">6</a>
<a href="#section-8">8</a>. Acknowledgements.............................................. <a href="#page-7">7</a>
<span class="grey">Kreuter Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4040">RFC 4040</a> 64 kbit/s Voice Band Data Call April 2005</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Voice over IP (VoIP) Media Gateways need to carry all possible data
streams generated by analog terminals or integrated services digital
network (ISDN) terminals via an IP network. Within this document a
VoIP Media Gateway is a device that converts a (digital or analog)
linear data stream to a digital packetized data stream or vice versa.
Refer to <a href="./rfc2719">RFC 2719</a> [<a href="#ref-10" title=""Framework Architecture for Signaling Transport"">10</a>] for an introduction into the basic
architecture of a Media Gateway based network.
Usually a VoIP Media Gateway does some processing on the data it
converts besides packetization or depacketization; i.e. echo
cancellation or dual tone multifrequency (DTMF) detection, and
especially a coding/decoding. But there is a class of data streams
that does not rely on or allow any data processing within the VoIP
Media Gateway except for packetization or depacketization. ISDN data
terminals i.e. will produce data streams that are not compatible with
a non-linear encoding as used for voice.
For such applications, there is a necessity for a transparent relay
of 64 kbit/s data streams in real-time transport protocol (RTP) [<a href="#ref-4" title=""RTP: A Transport Protocol for Real-Time Applications"">4</a>]
packets. This mode is often referred to as "clear-channel data" or
"64 kbit/s unrestricted". No encoder/decoder is needed in that case,
but a unique RTP payload type is necessary and a related MIME type is
to be registered for signaling purposes.
Clearmode is not restricted to the examples described above. It can
be used by any application, that does not need a special
encoding/decoding for transfer via a RTP connection.
This payload format document describes a pseudo-codec called
"Clearmode", for sample oriented 64 kbit/s data streams with 8 bits
per sample. It is in accordance with <a href="./rfc2736">RFC 2736</a> [<a href="#ref-1" title=""Guidelines for Writers of RTP Payload Format Specifications"">1</a>], which provides a
guideline for the specification of new RTP payload formats.
Examples for the current use of Clearmode are the transfer of "ISDN 7
kHz voice" and "ISDN data" in VoIP Media Gateways.
This document also serves as the MIME type registration according to
<a href="./rfc2045">RFC 2045</a> [<a href="#ref-2" title=""Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"">2</a>] and <a href="./rfc2048">RFC 2048</a> [<a href="#ref-3" title=""Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures"">3</a>], which defines procedures for
registration of new MIME types within the IETF tree.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-8" title=""Key words for use in RFCs to Indicate Requirement Levels"">8</a>].
<span class="grey">Kreuter Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4040">RFC 4040</a> 64 kbit/s Voice Band Data Call April 2005</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. 64 kbit/s Data Stream Handling and RTP Header Parameters</span>
Clearmode does not use any encoding or decoding. It just provides
packetization.
Clearmode assumes that the data to be handled is sample oriented with
one octet (8bits) per sample. There is no restriction on the number
of samples per packet other than the 64 kbyte limit imposed by the IP
protocol. The number of samples SHOULD be less than the path maximum
transmission unit (MTU) minus combined packet header length. If the
environment is expected to have tunnels or security encapsulation as
part of operation, the number of samples SHOULD be reduced to allow
for the extra header space.
The payload packetization/depacketization for Clearmode is similar to
the Pulse Code Modulation (PCMU or PCMA) handling described in <a href="./rfc3551">RFC</a>
<a href="./rfc3551">3551</a> [<a href="#ref-5" title=""RTP Profile for Audio and Video Conferences with Minimal Control"">5</a>]. Each Clearmode octet SHALL be octet-aligned in an RTP
packet. The sign bit of each octet SHALL correspond to the most
significant bit of the octet in the RTP packet.
A sample rate of 8000 Hz MUST be used.
This calculates to a 64 kbit/s transmission rate per channel.
The Timestamp SHALL be set as described in <a href="./rfc3550">RFC 3550</a> [<a href="#ref-4" title=""RTP: A Transport Protocol for Real-Time Applications"">4</a>].
The marker bit is always zero. Silence suppression is not applicable
for Clearmode data streams.
The payload type is dynamically assigned and is not presented in this
document.
RTP header fields not mentioned here SHALL be used as specified in
<a href="./rfc3550">RFC 3550</a> [<a href="#ref-4" title=""RTP: A Transport Protocol for Real-Time Applications"">4</a>] and any applicable profile.
This document specifies the use of RTP over unicast and multicast UDP
as well as TCP. (This does not preclude the use of this definition
when RTP is carried by other lower-layer protocols.)
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
This document registers the following MIME subtype: audio/clearmode.
To: ietf-types@iana.org
Subject: Registration of MIME media type audio/clearmode
MIME media type name: audio
<span class="grey">Kreuter Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4040">RFC 4040</a> 64 kbit/s Voice Band Data Call April 2005</span>
MIME subtype name: clearmode
Required parameters: none
Optional parameters: ptime, maxptime
"ptime" gives the length of time in milliseconds
represented by the media in a packet, as described in <a href="./rfc2327">RFC</a>
<a href="./rfc2327">2327</a> [<a href="#ref-6" title=""SDP: Session Description Protocol"">6</a>].
"maxptime" represents the maximum amount of media, which
can be encapsulated in each packet, expressed as time in
milliseconds, as described in <a href="./rfc3267">RFC 3267</a> [<a href="#ref-9" title=""Real- Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs"">9</a>].
Encoding considerations:
This type is only defined for transfer via RTP [<a href="#ref-4" title=""RTP: A Transport Protocol for Real-Time Applications"">4</a>].
Security considerations:
See <a href="./rfc4040#section-6">Section 6 of RFC 4040</a>
Interoperability considerations: none
Published specification: <a href="./rfc4040">RFC 4040</a>
Applications, which use this media type:
Voice over IP Media Gateways, transferring "ISDN 64 kb/s
data", "ISDN 7 kHz voice", or other 64 kbit/s data streams
via an RTP connection
Note: the choice of the "audio" top-level MIME type was
made because the dominant uses of this pseudo-codec are
expected to telephony and voice-gateway-related. The
"audio" type allows the use of sharing of the port in the
SDP "m=" line with codecs such as audio/g711 [<a href="#ref-6" title=""SDP: Session Description Protocol"">6</a>], [<a href="#ref-7" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">7</a>], for
one example. This sharing is an important application and
would not be possible otherwise.
Additional information: none
Intended usage: COMMON
Author/Change controller:
IETF Audio/Video transport working group
delegated from the IESG
<span class="grey">Kreuter Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4040">RFC 4040</a> 64 kbit/s Voice Band Data Call April 2005</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Mapping to Session Description Protocol (SDP) Parameters</span>
Parameters are mapped to SDP [<a href="#ref-6" title=""SDP: Session Description Protocol"">6</a>] in a standard way.
o The MIME type (audio) goes in SDP "m=" as the media name.
o The MIME subtype (clearmode) goes in SDP "a=rtpmap" as the
encoding name.
o The optional parameters "ptime" and "maxptime" go in the SDP
"a=ptime" and "a=maxptime" attributes, respectively.
An example mapping is as follows:
audio/clearmode; ptime=10
m=audio 12345 RTP/AVP 97
a=rtpmap:97 CLEARMODE/8000
a=ptime:10
Note that the payload format (encoding) names defined in the RTP
Profile are commonly shown in upper case. MIME subtypes are commonly
shown in lower case. These names are case-insensitive in both
places.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
Implementations using the payload format defined in this
specification are subject to the security considerations discussed in
the <a href="./rfc3550">RFC 3550</a> [<a href="#ref-4" title=""RTP: A Transport Protocol for Real-Time Applications"">4</a>]. The payload format described in this document does
not specify any different security services. The primary function of
this payload format is to add a transparent transport for a 64 kbit/s
data stream.
Confidentiality of the media streams is achieved by encryption, for
example by application of the Secure RTP profile [<a href="#ref-11" title=""The Secure Real-time Transport Protocol (SRTP)"">11</a>].
As with any IP-based protocol, in some circumstances a receiver may
be overloaded simply by the receipt of too many packets, either
desired or undesired. Network-layer authentication MAY be used to
discard packets from undesired sources, but the processing cost of
the authentication itself may be too high. Overload can also occur,
if the sender chooses to use a smaller packetization period, than the
receiver can process. The ptime parameter can be used to negotiate
an appropriate packetization during session setup.
<span class="grey">Kreuter Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4040">RFC 4040</a> 64 kbit/s Voice Band Data Call April 2005</span>
In general RTP is not an appropriate transfer protocol for reliable
octet streams. TCP is better in those cases. Besides that, packet
loss due to congestion is as much an issue for clearmode, as for
other payload formats. Refer to <a href="./rfc3551">RFC 3551</a> [<a href="#ref-5" title=""RTP Profile for Audio and Video Conferences with Minimal Control"">5</a>], section 2, for a
discussion of this issue.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-1">1</a>] Handley, M. and C. Perkins, "Guidelines for Writers of RTP
Payload Format Specifications", <a href="https://www.rfc-editor.org/bcp/bcp36">BCP 36</a>, <a href="./rfc2736">RFC 2736</a>, December 1999.
[<a id="ref-2">2</a>] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Bodies",
<a href="./rfc2045">RFC 2045</a>, November 1996.
[<a id="ref-3">3</a>] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet
Mail Extensions (MIME) Part Four: Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP</a>
<a href="https://www.rfc-editor.org/bcp/bcp13">13</a>, <a href="./rfc2048">RFC 2048</a>, November 1996.
[<a id="ref-4">4</a>] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
"RTP: A Transport Protocol for Real-Time Applications", STD 64,
<a href="./rfc3550">RFC 3550</a>, July 2003.
[<a id="ref-5">5</a>] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video
Conferences with Minimal Control", STD 65, <a href="./rfc3551">RFC 3551</a>, July 2003.
[<a id="ref-6">6</a>] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", <a href="./rfc2327">RFC 2327</a>, April 1998.
[<a id="ref-7">7</a>] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
Session Description Protocol (SDP)", <a href="./rfc3264">RFC 3264</a>, June 2002.
[<a id="ref-8">8</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-9">9</a>] Sjoberg, J., Westerlund, M., Lakaniemi, A., and Q. Xie, "Real-
Time Transport Protocol (RTP) Payload Format and File Storage
Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate
Wideband (AMR-WB) Audio Codecs", <a href="./rfc3267">RFC 3267</a>, June 2002.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-10">10</a>] Ong, L., Rytina, I., Garcia, M., Schwarzbauer, H., Coene, L.,
Lin, H., Juhasz, I., Holdrege, M., and C. Sharp, "Framework
Architecture for Signaling Transport", <a href="./rfc2719">RFC 2719</a>, October 1999.
<span class="grey">Kreuter Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4040">RFC 4040</a> 64 kbit/s Voice Band Data Call April 2005</span>
[<a id="ref-11">11</a>] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)", <a href="./rfc3711">RFC</a>
<a href="./rfc3711">3711</a>, March 2004.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
The editor would like to acknowledge the help of the IETF AVT Working
Group and, in particular the help of Colin Perkins and Magnus
Westerlund for their intensive reviews and comments.
Author's Address
Ruediger Kreuter
Siemens AG
81730 Munich, Germany
EMail: ruediger.kreuter@siemens.com
<span class="grey">Kreuter Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4040">RFC 4040</a> 64 kbit/s Voice Band Data Call April 2005</span>
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
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>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Kreuter Standards Track [Page 8]
</pre>
|
