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
|
<pre>Network Working Group G. Parsons
Request for Comments: 3362 Nortel Networks
Category: Standards Track August 2002
<span class="h1">Real-time Facsimile (T.38) - image/t38</span>
<span class="h1">MIME Sub-type Registration</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 (2002). All Rights Reserved.
Abstract
This document describes the registration of the MIME sub-type
image/t38. The encoding is defined by ITU Recommendation T.38 and is
intended for use as an Session Description Protocol (SDP) media
descriptor.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</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="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>
[<a href="#ref-REQ" title=""Key words for use in RFCs to Indicate Requirement Levels"">REQ</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview</span>
This document describes the registration of the MIME sub-type
image/t38. The encoding is defined by [<a href="#ref-T.38" title="'Procedures for real-time Group 3 facsimile communication over IP networks'">T.38</a>] and is intended for use
as an SDP media descriptor.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. T.38 Definition</span>
ITU-T Recommendation T.38 [<a href="#ref-T.38" title="'Procedures for real-time Group 3 facsimile communication over IP networks'">T.38</a>] describes the technical features
necessary to transfer facsimile documents in real-time between two
standard Group 3 facsimile terminals over the Internet or other
networks using IP protocols. The Recommendation allows the use of
either TCP or UDP depending on the service environment.
<span class="grey">Parsons Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3362">RFC 3362</a> MIME Sub-type image/t38 August 2002</span>
ITU-T Recommendation T.38 [<a href="#ref-T.38" title="'Procedures for real-time Group 3 facsimile communication over IP networks'">T.38</a>] Annex D describes system level
requirements and procedures for internet aware facsimile
implementations and internet aware facsimile gateways conforming to
ITU-T T.38 to establish calls with other ITU-T T.38 implementations
using the procedures defined in IETF <a href="./rfc2543">RFC 2543</a> [<a href="#ref-SIP-99" title=""SIP: Session Initiation Protocol"">SIP-99</a>] and IETF <a href="./rfc2327">RFC</a>
<a href="./rfc2327">2327</a> [<a href="#ref-SDP" title=""SDP: Session Description Protocol"">SDP</a>].
Note that ITU-T T.38 Recommendation T.38 (04/02) [<a href="#ref-T.38" title="'Procedures for real-time Group 3 facsimile communication over IP networks'">T.38</a>] is an
aggregation of the original ITU-T Recommendation T.38 (06/98) [T.38-
98] and all of the subsequent Amendments and Corrigendum including
[<a href="#ref-T.38D-00" title="'SIP/SDP Call Establishment Procedures'">T.38D-00</a>]. While [<a href="#ref-T.38" title="'Procedures for real-time Group 3 facsimile communication over IP networks'">T.38</a>] and [<a href="#ref-T.38D-00" title="'SIP/SDP Call Establishment Procedures'">T.38D-00</a>] describe SIP procedures per
[<a href="#ref-SIP-99" title=""SIP: Session Initiation Protocol"">SIP-99</a>], the procedures can also be applied to the revised Session
Initiation Protocol specification [<a href="#ref-SIP" title=""SIP: Session Initiation Protocol"">SIP</a>].
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> image/t38 Usage</span>
Annex D of [<a href="#ref-T.38" title="'Procedures for real-time Group 3 facsimile communication over IP networks'">T.38</a>] describes that the image/t38 media type is intended
to indicate a T.38 media stream in SDP.
This media type registration is not intended for email usage.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Registration</span>
To: ietf-types@iana.org
Subject: Registration of Standard MIME media type image/t38
MIME media type name: image
MIME subtype name: t38
Required parameters: none
Optional parameters: none
Encoding considerations: Binary
Security considerations:
This content denotes a facsimile bit stream that may or
may not be encrypted.
Interoperability considerations :
This MIME media subtype is intended to be used as a
parameter by SDP in SIP call setup for T.38 as described in
ITU-T Rec. T.38 Annex D. Any use of this media type by
email applications is not defined and as a result is not
guaranteed to interoperate with a T.38 stream.
<span class="grey">Parsons Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3362">RFC 3362</a> MIME Sub-type image/t38 August 2002</span>
Published specification:
ITU-T Recommendation T.38, 'Procedures for real-time
Group 3 facsimile communication over IP networks', April
2002.
A copy of the T.38 specifications can be found at:
<a href="http://www.itu.int/rec/recommendation">http://www.itu.int/rec/recommendation</a>.asp?type=folders&
lang=e&parent=T-REC-T.38
Applications which use this media type:
Real-time facsimile (fax)
Additional information:
Magic number(s):
II (little-endian):
MM (big-endian):
File extension(s): .T38
Macintosh File Type Code(s): T38
Person & email address to contact for further information:
Glenn W. Parsons
gparsons@nortelnetworks.com
Intended usage: COMMON
Change controller: Glenn Parsons
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
Security considerations for this media type are discussed in the MIME
type registration that appears in <a href="#section-4">section 4</a>.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
[<a id="ref-REQ">REQ</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-MIME4">MIME4</a>] Freed, N. and N. Borenstein, "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.
<span class="grey">Parsons Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3362">RFC 3362</a> MIME Sub-type image/t38 August 2002</span>
[<a id="ref-SDP">SDP</a>] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", <a href="./rfc2327">RFC 2327</a>, April 1998.
[<a id="ref-SIP">SIP</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M. and E. Schooler,
"SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, June 2002.
[<a id="ref-SIP-99">SIP-99</a>] Handley, M., Schulzrinne, H., Schooler, E. and J.
Rosenberg, "SIP: Session Initiation Protocol", <a href="./rfc2543">RFC 2543</a>,
March 1999.
[<a id="ref-T.38">T.38</a>] ITU-T Recommendation T.38, 'Procedures for real-time Group
3 facsimile communication over IP networks', April 2002.
[<a id="ref-T.38-98">T.38-98</a>] ITU-T Recommendation T.38, 'Procedures for real-time Group
3 facsimile communication over IP networks', June 1998.
[<a id="ref-T.38D-00">T.38D-00</a>] ITU-T Recommendation T.38 Amendment 2 Annex D, 'SIP/SDP
Call Establishment Procedures', February 2000.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Authors' Address</span>
Glenn W. Parsons
Nortel Networks
P.O. Box 3511, Station C
Ottawa, ON K1Y 4H7
Canada
Phone: +1-613-763-7582
Fax: +1-613-763-2697
EMail: gparsons@nortelnetworks.com
<span class="grey">Parsons Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3362">RFC 3362</a> MIME Sub-type image/t38 August 2002</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Parsons Standards Track [Page 5]
</pre>
|
