Debian Codegraph @

rfc3839.html

raw
1 <pre>Network Working Group R. Castagno
2 Request for Comments: 3839 Nokia Mobile Phones
3 Category: Standards Track D. Singer
4 Apple Computer, Inc.
5 July 2004
6
7
8 <span class="h1">MIME Type Registrations for</span>
9 <span class="h1">3rd Generation Partnership Project (3GPP) Multimedia files</span>
10
11 Status of this Memo
12
13 This document specifies an Internet standards track protocol for the
14 Internet community, and requests discussion and suggestions for
15 improvements. Please refer to the current edition of the "Internet
16 Official Protocol Standards" (STD 1) for the standardization state
17 and status of this protocol. Distribution of this memo is unlimited.
18
19 Copyright Notice
20
21 Copyright (C) The Internet Society (2004).
22
23 Abstract
24
25 This document serves to register and document the standard MIME types
26 associated with the 3GPP multimedia file format, which is part of the
27 family based on the ISO Media File Format.
28
29 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
30
31 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
32 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
33 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>
34 [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
35
36 The third-generation partnership project (3GPP) for third-generation
37 cellular telephony has defined a standard file format to contain
38 audio/visual sequences which may be downloaded to cellular phones
39 [<a href="#ref-3GPP">3GPP</a>]. At the time of writing, the 3GPP file format (3GP) can
40 contain H.263 or MPEG-4 video, and AMR Narrow-band speech, AMR wide-
41 band speech, or AAC audio, and 3GPP timed text.
42
43 Within the file, as with all files in the 'ISO' family, there is an
44 intrinsic file-type box, which identifies those specifications to
45 which the file complies, and which players (possibly compliant with
46 only one specification) are permitted by the content author to play
47 the file. This identification is through four-letter 'brands'.
48
49
50
51
52 <span class="grey">Castagno &amp; Singer 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="./rfc3839">RFC 3839</a> MIME Type Registrations for 3GPP July 2004</span>
55
56
57 Files identified by the MIME [<a href="#ref-MIME1" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">MIME1</a>] type defined here MUST contain a
58 brand defined in a standard issued by 3GPP that can apply to 3GPP
59 files, in their compatible brands list.
60
61 The MIME types defined here are needed to correctly identify such
62 files when they are served over HTTP, included in multi-part
63 documents, or used in other places where MIME types are used.
64
65 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Security Considerations</span>
66
67 The 3GPP file format may contain audio, video, and displayable text
68 data. There is currently no provision for 'active' elements (such as
69 scripts) of any kind.
70
71 Clearly it is possible to author malicious files which attempt to
72 call for an excessively large picture size, high sampling-rate audio
73 etc. However, clients can and usually do protect themselves against
74 this kind of attack.
75
76 It should be noted that selected metadata fields may encompass
77 information partly intended to protect the media against unauthorized
78 use or distribution. In this case, the intention is that alteration
79 or removal of the data in the field would be treated as an offense
80 under national agreements based on World Intellectual Property
81 Organization (WIPO) treaties.
82
83 3GPP files have an extensible structure, so that it is theoretically
84 possible that metadata fields or media formats could be defined in
85 the future which could be used to induce particular actions on the
86 part of the recipient, thus presenting additional security risks.
87 However, this type of capability is currently not supported in the
88 referenced specification.
89
90 There is no current provision in the standards for encryption,
91 signing, or authentication of these file formats.
92
93 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. MIME Types</span>
94
95 This registration applies to all files defined as using the '3GP'
96 file format and identified with a suitable brand in a 3GPP
97 specification. The usual file suffix for all these files is ".3gp".
98
99 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Files with audio but no video</span>
100
101 The type "audio/3gpp" may be used for files containing audio but no
102 visual presentation (neither video nor timed text, for example).
103
104
105
106
107
108 <span class="grey">Castagno &amp; Singer 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="./rfc3839">RFC 3839</a> MIME Type Registrations for 3GPP July 2004</span>
111
112
113 To: [email protected]
114 Subject: Registration of Standard MIME media type audio/3gpp
115
116 MIME media type name: audio
117 MIME subtype name: 3gpp
118 Required parameters: none
119 Optional parameters: none
120 Ongoing work related to this
121 registration may introduce new
122 optional parameters. One example
123 area of effort may introduce a
124 parameter that would allow for
125 codecs in use within the MIME type
126 to be asserted and determined
127 without examination of the file.
128 Those with interests in the area
129 should monitor registrations for
130 updates.
131 Encoding considerations: files are binary and should be
132 transmitted in a suitable encoding
133 without CR/LF conversion, 7-bit
134 stripping etc.; base64 is a suitable
135 encoding. Note that this MIME type
136 is used only for files; separate
137 types are used for real-time
138 transfer, such as for the RTP
139 payload format for AMR audio
140 [<a href="./rfc3267" title="&quot;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&quot;">RFC3267</a>].
141 Security considerations: see the security considerations
142 section in <a href="./rfc3839">RFC 3839</a>
143 Interoperability considerations: The 3GPP organization has defined the
144 specification, interoperability, and
145 conformance, and conducts regular
146 interoperability testing.
147 Published specification: 3GPP 26.234, Release 5; 3GPP 26.244,
148 Release 6 or later. 3GPP
149 specifications are publicly
150 accessible at the 3GPP web site,
151 www.3gpp.org.
152 Applications which use this media type: Multi-media
153 Additional information: The type "audio/3gpp" MAY be used for
154 files containing audio but no visual
155 presentation. Files served under
156 this type MUST NOT contain any
157 visual material. (Note that 3GPP
158 timed text is visually presented
159 and is considered to be visual
160 material).
161
162
163
164 <span class="grey">Castagno &amp; Singer 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="./rfc3839">RFC 3839</a> MIME Type Registrations for 3GPP July 2004</span>
167
168
169 Magic number(s): None. However, the file-type box
170 must occur first in the file, and
171 MUST contain a 3GPP brand in its
172 compatible brands list.
173 File extension(s): 3gp and 3gpp are both declared at
174 <a href="http://www.nist">http://www.nist</a>.gov/nics/; 3gp is
175 preferred
176 Macintosh File Type Code(s): '3gpp'
177 Person &amp; email address to contact for further information:
178 Nokia MIME manager, [email protected]
179 Intended usage: COMMON
180 Change controller: 3GPP
181
182 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Any files</span>
183
184 The type "video/3gpp" is valid for all files. It is valid to serve
185 an audio-only file as "video/3gpp".
186
187 To: [email protected]
188 Subject: Registration of Standard MIME media type video/3gpp
189
190 MIME media type name: video
191 MIME subtype name: 3gpp
192 Required parameters: none
193 Optional parameters: none
194 Encoding considerations: files are binary and should be
195 transmitted in a suitable encoding
196 without CR/LF conversion, 7-bit
197 stripping etc.; base64 is a suitable
198 encoding. Note that this MIME type
199 is used only for files; separate
200 types are used for real-time
201 transfer, such as for the RTP
202 payload formats for H.263
203 [<a href="./rfc2429" title="&quot;RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)&quot;">RFC2429</a>] and AMR audio
204 [<a href="./rfc3267" title="&quot;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&quot;">RFC3267</a>].
205 Security considerations: see the security considerations
206 section in <a href="./rfc3839">RFC 3839</a>
207 Interoperability considerations: The 3GPP organization has defined the
208 specification, interoperability, and
209 conformance, and conducts regular
210 interoperability testing.
211 Published specification: 3GPP 26.234, Release 5; 3GPP 26.244,
212 Release 6 or later. 3GPP
213 specifications are publicly
214 accessible at the 3GPP web site,
215 www.3gpp.org.
216 Applications which use this media type: Multi-media
217
218
219
220 <span class="grey">Castagno &amp; Singer 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="./rfc3839">RFC 3839</a> MIME Type Registrations for 3GPP July 2004</span>
223
224
225 Additional information:
226 Magic number(s): None. However, the file-type box
227 must occur first in the file, and
228 MUST contain a 3GPP brand in its
229 compatible brands list.
230 File extension(s): 3gp and 3gpp are both declared at
231 <a href="http://www.nist">http://www.nist</a>.gov/nics/; 3gp is
232 preferred
233 Macintosh File Type Code(s): '3gpp'
234 Person &amp; email address to contact for further information:
235 Nokia MIME manager, [email protected]
236 Intended usage: COMMON
237 Change controller: 3GPP
238
239 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
240
241 This document registers the MIME types audio/3gpp and video/3gpp,
242 defined above.
243
244 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
245
246 The review of the 3GPP SA4 committee is gratefully acknowledged, in
247 particular Per Frojdh. The chairs of the AVT working group, in
248 particular Colin Perkins, have provided both excellent guidance and
249 feedback, for which the authors are grateful.
250
251 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
252
253 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
254
255 [<a id="ref-3GPP">3GPP</a>] Published specifications in releases 5 and 6: Release 5:
256 3GPP TS 26.234: Transparent end-to-end packet switched
257 streaming service (PSS); Protocols and codecs. Release 6:
258 3GPP TS 26.244: Transparent end-to-end packet switched
259 streaming service (PSS); 3GPP file format (3GP)
260
261 [<a id="ref-MIME1">MIME1</a>] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
262 Extensions (MIME) Part One: Format of Internet Message
263 Bodies", <a href="./rfc2045">RFC 2045</a>, November 1996.
264
265 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
266 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
267
268
269
270
271
272
273
274
275
276 <span class="grey">Castagno &amp; Singer 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="./rfc3839">RFC 3839</a> MIME Type Registrations for 3GPP July 2004</span>
279
280
281 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
282
283 [<a id="ref-RFC2429">RFC2429</a>] Bormann, C., Cline, L., Deisher, G., Gardos, T., Maciocco,
284 C., Newell, D., Ott, J., Sullivan, G., Wenger, S. and C.
285 Zhu, "RTP Payload Format for the 1998 Version of ITU-T Rec.
286 H.263 Video (H.263+)", <a href="./rfc2429">RFC 2429</a>, October 1998.
287
288 [<a id="ref-RFC3267">RFC3267</a>] Sjoberg, J., Westerlund, M., Lakaniemi, A. and Q. Xie,
289 "Real-Time Transport Protocol (RTP) Payload Format and File
290 Storage Format for the Adaptive Multi-Rate (AMR) and
291 Adaptive Multi-Rate WideBand (AMR-WB) Audio Codecs", <a href="./rfc3267">RFC</a>
292 <a href="./rfc3267">3267</a>, June 2002.
293
294 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Authors' Contact Information</span>
295
296 Roberto Castagno
297 Nokia Mobile Phones
298 PO Box 88, FIN-33721 Tampere
299 (Tieteenkatu 1, FIN-33720 Tampere)
300 Finland
301
302 Phone: +358 7180 35796
303 EMail: [email protected]
304
305
306 David Singer
307 Apple Computer, Inc.
308 One Infinite Loop, MS:302-3MT
309 Cupertino CA 95014
310 USA
311
312 Phone: +1 408 974 3162
313 EMail: [email protected]
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Castagno &amp; Singer 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="./rfc3839">RFC 3839</a> MIME Type Registrations for 3GPP July 2004</span>
335
336
337 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Full Copyright Statement</span>
338
339 Copyright (C) The Internet Society (2004). This document is subject
340 to the rights, licenses and restrictions contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and
341 except as set forth therein, the authors retain all their rights.
342
343 This document and the information contained herein are provided on an
344 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
345 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
346 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
347 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
348 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
349 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
350
351 Intellectual Property
352
353 The IETF takes no position regarding the validity or scope of any
354 Intellectual Property Rights or other rights that might be claimed to
355 pertain to the implementation or use of the technology described in
356 this document or the extent to which any license under such rights
357 might or might not be available; nor does it represent that it has
358 made any independent effort to identify any such rights. Information
359 on the procedures with respect to rights in RFC documents can be
360 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>.
361
362 Copies of IPR disclosures made to the IETF Secretariat and any
363 assurances of licenses to be made available, or the result of an
364 attempt made to obtain a general license or permission for the use of
365 such proprietary rights by implementers or users of this
366 specification can be obtained from the IETF on-line IPR repository at
367 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
368
369 The IETF invites any interested party to bring to its attention any
370 copyrights, patents or patent applications, or other proprietary
371 rights that may cover technology that may be required to implement
372 this standard. Please address the information to the IETF at ietf-
373 [email protected].
374
375 Acknowledgement
376
377 Funding for the RFC Editor function is currently provided by the
378 Internet Society.
379
380
381
382
383
384
385
386
387
388 Castagno &amp; Singer Standards Track [Page 7]
389 </pre>