idnits 2.17.1
draft-lim-mpeg4-mime-03.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** It looks like you're using RFC 3978 boilerplate. You should update this
to the boilerplate described in the IETF Trust License Policy document
(see https://trustee.ietf.org/license-info), which is required now.
-- Found old boilerplate from RFC 3667, Section 5.1 on line 13.
-- Found old boilerplate from RFC 3978, Section 5.5 on line 353.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 364.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 371.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 377.
** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure
Acknowledgement -- however, there's a paragraph with a matching
beginning. Boilerplate error?
** This document has an original RFC 3978 Section 5.4 Copyright Line,
instead of the newer IETF Trust Copyright according to RFC 4748.
** This document has an original RFC 3978 Section 5.5 Disclaimer, instead
of the newer disclaimer which includes the IETF Trust according to RFC
4748.
** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate
instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission
of drafts without verbatim RFC 3978 boilerplate is not accepted.
The following non-3978 patterns matched text found in the document.
That text should be removed or replaced:
By submitting this Internet-Draft, I certify that any applicable patent
or other IPR claims of which I am aware have been disclosed, or
will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
== The page length should not exceed 58 lines per page, but there was 1
longer page, the longest (page 11) being 78 lines
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
No issues found here.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
match the current year
== Unrecognized Status in 'Category:', assuming Proposed Standard
(Expected one of 'Standards Track', 'Full Standard', 'Draft Standard',
'Proposed Standard', 'Best Current Practice', 'Informational',
'Experimental', 'Informational', 'Historic'.)
-- The document seems to lack a disclaimer for pre-RFC5378 work, but may
have content which was first submitted before 10 November 2008. If you
have contacted all the original authors and they are all willing to grant
the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
this comment. If not, you may need to add the pre-RFC5378 disclaimer.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (March 2005) is 6981 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
-- Missing reference section? '3' on line 63 looks like a reference
Summary: 5 errors (**), 0 flaws (~~), 3 warnings (==), 8 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
1 Audio-Video Transport WG Y Lim, D. Singer
2 Internet Draft net&tv, Apple Computer
3 Document: draft-lim-mpeg4-mime-03 October 2004
4 Category: Expires March 2005
6 MIME Type Registration for MPEG-4
8 Status of this Memo
10 By submitting this Internet-Draft, I certify that any applicable
11 patent or other IPR claims of which I am aware have been disclosed,
12 and any of which I become aware will be disclosed, in accordance with
13 RFC 3668.
15 Internet-Drafts are working documents of the Internet Engineering
16 Task Force (IETF), its areas, and its working groups. Note that
17 other groups may also distribute working documents as
18 Internet-Drafts.
20 Internet-Drafts are draft documents valid for a maximum of six
21 months and may be updated, replaced, or obsoleted by other documents
22 at any time. It is inappropriate to use Internet-Drafts as
23 reference material or to cite them other than as "work in progress."
25 The list of current Internet-Drafts can be accessed at
26 http://www.ietf.org/1id-abstracts.txt
28 The list of Internet-Draft Shadow Directories can be accessed at
29 http://www.ietf.org/shadow.html
31 This document is a submission of the IETF AVT WG. Comments should
32 be directed to the AVT WG mailing list, avt@ietf.org.
34 Abstract
36 This document defines the standard MIME types associated with MP4
37 files. This also document recommended use of registered MIME types
38 according to the type of contents.
40 Table of Contents
42 1. Introduction...................................................3
43 2. Selection of MIME types for MP4 files..........................3
44 3. IANA Considerations............................................4
45 3.1 MP4 file with visual presentation..........................4
46 3.2 MP4 file without visual presentation.......................5
47 3.3 MP4 file without visual presentation.......................6
48 3.4 IOD in binary format.......................................7
49 3.5 IOD in textual format......................................8
50 4. Security Considerations........................................9
51 5. Acknowledgments................................................9
52 6. Full Copyright Statement......................................10
53 7. Intellectual Property Notice..................................10
54 8. References....................................................11
55 9. Author's Addresses............................................11
56 1. Introduction
58 This document describes standard definition of MIME types associated
59 with MP4 files and the guidelines for using them.
61 MPEG-4, ISO/IEC 14496, is a standard designed for the representation
62 and delivery of multimedia information over a variety of transport
63 protocols[3]. It includes interactive scene management, visual and
64 audio representations as well as systems functionality like
65 multiplexing, synchronization, and an object descriptor framework.
67 The historical approach for MPEG data is to declare it under "video",
68 and this approach is followed for ISO/IEC 14496. In addition some
69 MIME types are defined under "audio" and "application" for the
70 streams not containing visual presentation.
72 Amendment 1 of the ISO/IEC 14496 standard (also known as version 2)
73 includes a standard file type for encapsulating ISO/IEC 14496 data.
74 This file type can be used in a number of ways: perhaps the most
75 important are its use as an interchange format for ISO/IEC 14496
76 data, its use as a content-download format, and as the format read by
77 streaming media servers.
79 These first two uses will be greatly facilitated if there is a
80 standard MIME type for serving these files (e.g. over HTTP).
82 The ISO/IEC 14496 standard is broad, and therefore the type of data
83 that may be in such a file can vary. In brief, simple compressed
84 video and audio (using a number of different compression algorithms)
85 can be included; interactive scene information; meta-data about the
86 presentation; references to ISO/IEC 14496 media streams outside the
87 file and so on. Different top-level MIME types are used to identify
88 the type of the contents in the file.
90 2. Selection of MIME types for MP4 file
92 The MIME types to be assigned to MP4 files are selected based on the
93 contents. Basic guidelines of selecting MIME types are as follows:
95 a) if the file contains neither visual nor audio presentations, but
96 only for example MPEG-J or MPEG-7, use application/mp4
98 b) for all other files, including those which have MPEG-J etc. in
99 addition to video or audio streams, video/mp4 should be used,
100 although:
102 c) for files with audio but no visual aspect, including those which
103 have MPEG-J etc. in addition to audio streams, audio/mp4 may be used.
105 In either case, these indicate files conforming to the "MP4"
106 specification (ISO/IEC 14496-1:2000, systems file format).
108 3. IANA Considerations
110 This section describes the MIME types and names to be used with
111 various MPEG-4 contents. Sections from 4.1 to 4.5 register five new
112 MIME types.
114 3.1 MP4 file
116 MIME media type name: video
118 MIME subtype name: mp4
120 Required parameters: none
122 Optional parameters: none
124 Encoding considerations: base64 generally preferred; files are
125 binary and should be transmitted without CR/LF conversion, 7-bit
126 stripping etc.
128 Security considerations: See section 5 of RFC XXXX
130 Interoperability considerations: A number of interoperating
131 implementations exist within the ISO/IEC 14496 community; and that
132 community has reference software for reading and writing the file
133 format.
135 Published specification: ISO/IEC 14496-1:2001.
137 Applications: Multimedia
139 Additional information:
141 Magic number(s): none
142 File extension(s): mp4 and mpg4 are both declared at
143
144 Macintosh File Type Code(s): mpg4 is registered with Apple
146 Person to contact for info: David Singer, singer@apple.com
148 Intended usage: Common
150 Author/Change controller: David Singer, ISO/IEC 14496 file format
151 chair
152 3.2 MP4 file with audio but without visual presentation
154 MIME media type name:audio
156 MIME subtype name: mp4
158 Required parameters: none
160 Optional parameters: none
162 Encoding considerations: base64 generally preferred; files are
163 binary and should be transmitted without CR/LF conversion, 7-bit
164 stripping etc.
166 Security considerations: See section 5 of RFC XXXX
168 Interoperability considerations: A number of interoperating
169 implementations exist within the ISO/IEC 14496 community; and that
170 community has reference software for reading and writing the file
171 format.
173 Published specification: ISO/IEC 14496-1:2001.
175 Applications: Multimedia
177 Additional information:
179 Magic number(s): none
180 File extension(s): mp4 and mpg4 are both declared at
181
182 Macintosh File Type Code(s): mpg4 is registered with Apple
184 Person to contact for info: David Singer, singer@apple.com
186 Intended usage: Common
188 Author/Change controller: David Singer, ISO/IEC 14496 file format
189 chair
190 3.3 MP4 file with MPEG-4 system stream and
191 neither visual nor audio presentation
193 MIME media type name:application
195 MIME subtype name: mp4
197 Required parameters: none
199 Optional parameters: none
201 Encoding considerations: base64 generally preferred; files are
202 binary and should be transmitted without CR/LF conversion, 7-bit
203 stripping etc.
205 Security considerations: See section 5 of RFC XXXX
207 Interoperability considerations: A number of interoperating
208 implementations exist within the ISO/IEC 14496 community; and that
209 community has reference software for reading and writing the file
210 format.
212 Published specification: ISO/IEC 14496-1:2001.
214 Applications: Multimedia
216 Additional information:
218 Magic number(s): none
219 File extension(s): mp4 and mpg4 are both declared at
220
221 Macintosh File Type Code(s): mpg4 is registered with Apple
223 Person to contact for info: David Singer, singer@apple.com
225 Intended usage: Common
227 Author/Change controller: David Singer, ISO/IEC 14496 file format
228 chair
229 3.4 IOD in binary format
231 MIME media type name: application
233 MIME subtype name: mpeg4-iod
235 Required parameters: none
237 Optional parameters: none
239 Encoding considerations: base64 generally preferred; files are
240 binary and should be transmitted without CR/LF conversion, 7-bit
241 stripping etc.
243 Security considerations: See section 5 of RFC XXXX
245 Interoperability considerations: A number of interoperating
246 implementations exist within the ISO/IEC 14496 community; and that
247 community has reference software for reading and writing the file
248 format.
250 Published specification: ISO/IEC 14496-1:2001
252 Applications: Multimedia
254 Additional information:
256 Magic number(s): none
257 File extension(s): none mp4 and mpg4 are both declared at
258
259 Macintosh File Type Code(s): mpg4 is registered with Apple
261 Person to contact for info: David Singer, singer@apple.com
263 Intended usage: Common
265 Author/Change controller: David Singer, ISO/IEC 14496 file format
266 chair
267 3.5 IOD in textual format
269 MIME media type name: application
271 MIME subtype name: mpeg4-iod-xmt
273 Required parameters: none
275 Optional parameters: none
277 Encoding considerations: none
279 Security considerations: See section 5 of RFC XXXX
281 Interoperability considerations: A number of interoperating
282 implementations exist within the ISO/IEC 14496 community; and that
283 community has reference software for reading and writing the file
284 format.
286 Published specification: ISO/IEC 14496-1:2001 AMD2.
288 Applications: Multimedia
290 Additional information:
292 Magic number(s): none
293 File extension(s): mp4 and mpg4 are both declared at
294
295 Macintosh File Type Code(s): mpg4 is registered with Apple
297 Person to contact for info: David Singer, singer@apple.com
299 Intended usage: Common
301 Author/Change controller: David Singer, ISO/IEC 14496 file format
302 chair
303 4. Security Considerations
305 It is possible to inject non-compliant MPEG streams (Audio, Video,
306 and Systems) in the MP4 file to overload the receiver/decoder's
307 buffers which might compromise the functionality of the receiver
308 or even crash it. This is especially true for end-to-end systems
309 like MPEG where the buffer models are precisely defined.
311 MP4 file supports storage of stream types including commands that
312 are executed on the terminal like OD commands, BIFS commands, etc.
313 and programmatic content like MPEG-J (Java(TM) Byte Code) and
314 ECMASCRIPT. It is possible to use one or more of the above in a
315 manner non-compliant to MPEG to crash or temporarily make the
316 receiver unavailable.
318 Authentication mechanisms can be used to validate of the sender and
319 the data to prevent security problems due to non-compliant malignant
320 MP4 file.
322 A security model is defined in ISO/IEC 14496 Systems MP4 files
323 containing MPEG-J contents which comprises Java(TM) classes and
324 objects. MPEG-J defines a set of Java APIs and a secure execution
325 model. MPEG-J content can call this set of APIs and Java(TM) methods
326 from a set of Java packages supported in the receiver within the
327 defined security model. According to this security model, downloaded
328 byte code is forbidden to load libraries, define native methods,
329 start programs, read or write files, or read system properties.
331 5. Acknowledgments
333 This draft has benefited greatly by contributions from many people,
334 including Mike Coleman, Jean-Claude Duford, Viswanathan Swaminathan,
335 Peter Westerink, Carsten Herpel, Olivier Avaro, Paul Christ, Zvi
336 Lifshitz, and many others. Their insight, foresight, and
337 contribution is gratefully acknowledged. Little has been invented
338 here by the author; this is mostly a collation of greatness that has
339 gone before.
341 6. Full Copyright Statement
343 Copyright (C) The Internet Society (2004). This document is subject
344 to the rights, licenses and restrictions contained in BCP 78, and
345 except as set forth therein, the authors retain all their rights.
347 This document and the information contained herein are provided on
348 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
349 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
350 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
351 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
352 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
353 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
355 7. Intellectual Property Notice
357 The IETF takes no position regarding the validity or scope of any
358 Intellectual Property Rights or other rights that might be claimed
359 to pertain to the implementation or use of the technology described
360 in this document or the extent to which any license under such
361 rights might or might not be available; nor does it represent that
362 it has made any independent effort to identify any such rights.
363 Information on the procedures with respect to rights in RFC
364 documents can be found in BCP 78 and BCP 79.
366 Copies of IPR disclosures made to the IETF Secretariat and any
367 assurances of licenses to be made available, or the result of an
368 attempt made to obtain a general license or permission for the use
369 of such proprietary rights by implementers or users of this
370 specification can be obtained from the IETF on-line IPR repository
371 at http://www.ietf.org/ipr.
373 The IETF invites any interested party to bring to its attention any
374 copyrights, patents or patent applications, or other proprietary
375 rights that may cover technology that may be required to implement
376 this standard. Please address the information to the IETF at ietf-
377 ipr@ietf.org.
379 8. References
380 8.1 Normative References
382 [1]Bradner, S., "The Internet Standards Process -- Revision 3", BCP
383 9, RFC 2026, October 1996.
385 [2]Bradner, S., "Key words for use in RFCs to Indicate Requirement
386 Levels", BCP 14, RFC 2119, March 1997
388 [3]H. Schulzrinne, et. al., "RTP : A Transport Protocol for Real-Time
389 Applications", IETF RFC 1889, January 1996.
391 [4]ISO/IEC 14496-1 "Information technology - Coding of audio-visual
392 objects - Part 1 : Systems", 3rd ed. 2004
394 [5]ISO/IEC 14496-12 "Information technology - Coding of audio-visual
395 objects - Part 12 : ISO Base Media File Format", December 2003
397 [6]ISO/IEC 14496-14 "Information technology - Coding of audio-visual
398 objects - Part 14 : MP4 File Format", January 2004
400 [7]ISO/IEC 14496-15 "Information technology - Coding of audio-visual
401 objects - Part 15 : AVC File Format", 2004
403 9. Author's Addresses
405 Young-Kwon LIM
406 net&tv Inc.
407 Room 802 Hanseo Building
408 1582-6 Seocho-3-Dong Seocho-Gu
409 Seoul, 137-875, Korea
410 E-mail : young@netntv.co.kr
411 TEL : +82-2-581-2305
413 David Singer
414 Apple Computer, Inc.
415 One Infinite Loop, MS:302-3MT
416 Cupertino CA 95014
417 USA
418 Email: singer@apple.com
419 Tel: +1 408 974 3162