| 1 |
<pre>Network Working Group T. Edwards |
| 2 |
Request for Comments: 4539 PBS |
| 3 |
Category: Informational May 2006 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Media Type Registration for the</span> |
| 7 |
<span class="h1">Society of Motion Picture and Television Engineers (SMPTE)</span> |
| 8 |
<span class="h1">Material Exchange Format (MXF)</span> |
| 9 |
|
| 10 |
Status of This Memo |
| 11 |
|
| 12 |
This memo provides information for the Internet community. It does |
| 13 |
not specify an Internet standard of any kind. Distribution of this |
| 14 |
memo is unlimited. |
| 15 |
|
| 16 |
Copyright Notice |
| 17 |
|
| 18 |
Copyright (C) The Internet Society (2006). |
| 19 |
|
| 20 |
Abstract |
| 21 |
|
| 22 |
This document serves to register a media type for the Society of |
| 23 |
Motion Picture and Television Engineers (SMPTE) Material Exchange |
| 24 |
Format (MXF). MXF, defined by SMPTE 377M, is a standard wrapper |
| 25 |
format developed for the interchange of audiovisual material, |
| 26 |
including both audiovisual essence and rich metadata. |
| 27 |
|
| 28 |
Table of Contents |
| 29 |
|
| 30 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 31 |
<a href="#section-2">2</a>. Security Considerations .........................................<a href="#page-3">3</a> |
| 32 |
<a href="#section-3">3</a>. IANA Considerations .............................................<a href="#page-3">3</a> |
| 33 |
<a href="#section-3.1">3.1</a>. Media Type for SMPTE Material Exchange Format (MXF) ........<a href="#page-3">3</a> |
| 34 |
<a href="#section-4">4</a>. References ......................................................<a href="#page-5">5</a> |
| 35 |
<a href="#section-4.1">4.1</a>. Normative References .......................................<a href="#page-5">5</a> |
| 36 |
<a href="#section-4.2">4.2</a>. Informative References .....................................<a href="#page-5">5</a> |
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Edwards Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc4539">RFC 4539</a> Media Type Registration for MXF May 2006</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
The present document registers a media type for SMPTE Material |
| 60 |
Exchange Format (MXF). MXF, defined by SMPTE 377M [<a href="#ref-SMPTE377M" title=""Material Exchange Format (MXF) File Format Specification"">SMPTE377M</a>], is a |
| 61 |
standard wrapper format developed for the interchange of audiovisual |
| 62 |
material, including both audiovisual essence and rich metadata. |
| 63 |
|
| 64 |
Essence is the raw video, audio, and data streams contained and |
| 65 |
described by MXF. Metadata carried by MXF includes structural |
| 66 |
metadata and descriptive metadata. Structural metadata relates to |
| 67 |
the structure and capabilities of the MXF file and is generally |
| 68 |
required for proper decoding. Some examples of structural metadata |
| 69 |
are descriptions of essence types, information to help synchronize |
| 70 |
playout of audio and video, and content length. Descriptive metadata |
| 71 |
gives information about the program content in the file and is not |
| 72 |
essential for decoding. Some examples of descriptive metadata are |
| 73 |
program title, actors, and scene descriptions. The essence in MXF |
| 74 |
files may itself carry data, such as vertical blanking interval data |
| 75 |
used for carriage of Closed Captioning and other purposes. |
| 76 |
|
| 77 |
MXF is an important tool in providing interoperation between |
| 78 |
different video systems as well as digital cinema systems. MXF also |
| 79 |
aids in the development of video production and distribution |
| 80 |
workflows that are more efficient, multi-vendor, file based, and IT |
| 81 |
oriented. |
| 82 |
|
| 83 |
SMPTE currently has standards for the mapping of the following |
| 84 |
essence types to the MXF generic container: MPEG (including MPEG-1 |
| 85 |
and MPEG-2 video streams, as well as MPEG audio), DV-DIF (Digital |
| 86 |
Video Digital Interface Format for the DV family of related video |
| 87 |
encodings), Uncompressed Pictures, SDTI-CP (Serial Digital Transport |
| 88 |
Interface Content Package for delivering packetized audiovisual |
| 89 |
content over the SDI interface), D-10 (a specialized video stream |
| 90 |
incorporating MPEG-2 4:2:2P@ML), D-11 (a high-definition video |
| 91 |
compression standard), AES3 audio, Broadcast Wave audio, and A-Law |
| 92 |
audio. The flexibility of the MXF generic container allows for the |
| 93 |
possibility of mappings of additional essence types in the future. |
| 94 |
|
| 95 |
The media type defined here is needed to correctly identify MXF files |
| 96 |
when they are served over HTTP or other network connections, included |
| 97 |
in multi-part documents, indexed by operating systems and digital |
| 98 |
asset management systems, or used in other places where media types |
| 99 |
are used. |
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Edwards Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc4539">RFC 4539</a> Media Type Registration for MXF May 2006</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Security Considerations</span> |
| 114 |
|
| 115 |
Security requirements for the application/mxf media type are |
| 116 |
discussed in the IANA media type registration (<a href="#section-3.1">Section 3.1</a>). |
| 117 |
|
| 118 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span> |
| 119 |
|
| 120 |
The IANA has registered the media type application/mxf as specified |
| 121 |
in <a href="#section-3.1">Section 3.1</a>. The registration uses the template present in |
| 122 |
[<a href="./rfc4288" title=""Media Type Specifications and Registration Procedures"">RFC4288</a>]. |
| 123 |
|
| 124 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Media Type for SMPTE Material Exchange Format (MXF)</span> |
| 125 |
|
| 126 |
To: [email protected] |
| 127 |
Subject: Registration of media type application/mxf |
| 128 |
|
| 129 |
Type name: application |
| 130 |
|
| 131 |
Subtype name: mxf |
| 132 |
|
| 133 |
Required parameters: none |
| 134 |
|
| 135 |
Optional parameters: ULs |
| 136 |
|
| 137 |
The optional parameter ULs is a single Uniform Resource Name (URN), |
| 138 |
or a comma-separated list of multiple URNs of SMPTE Universal Labels |
| 139 |
(which are defined by SMPTE 400M [<a href="#ref-SMPTE400M" title=""SMPTE Labels Structure"">SMPTE400M</a>]). |
| 140 |
|
| 141 |
This optional parameter provides hints to the decoder regarding the |
| 142 |
structure of the MXF file, which could include Operational Pattern, |
| 143 |
essence types, descriptive metadata schemes, and other elements that |
| 144 |
are identified by their SMPTE Universal Label. |
| 145 |
|
| 146 |
SMPTE Universal Labels are Object Identifiers (OIDs), as specified by |
| 147 |
[<a href="#ref-ASN1" title=""Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)"">ASN1</a>]. Thus, a URN of a SMPTE Universal Label can use the OID URN |
| 148 |
namespace specified in [<a href="./rfc3061" title=""A URN Namespace of Object Identifiers"">RFC3061</a>], or any other future URN namespace |
| 149 |
that is appropriate for SMPTE Universal Labels. |
| 150 |
|
| 151 |
Note that, per [<a href="./rfc2045" title=""Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"">RFC2045</a>], some characters (including the comma used |
| 152 |
to separate multiple values) require that the entire parameter value |
| 153 |
be enclosed in quotes. |
| 154 |
|
| 155 |
Below is an example of use of the optional parameter. The two SMPTE |
| 156 |
Universal Labels indicate that the MXF file uses the OP1a Operational |
| 157 |
Pattern and contains IEC DV video at 25 Mbps, 525 lines, 59.94 fps |
| 158 |
interlaced essence. |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Edwards Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc4539">RFC 4539</a> Media Type Registration for MXF May 2006</span> |
| 167 |
|
| 168 |
|
| 169 |
Content-Type: application/mxf; |
| 170 |
ULs="urn:oid:1.3.52.4.1.1.1.13.1.2.1.1.1, |
| 171 |
urn:oid:1.3.52.4.1.1.1.4.1.2.2.2.1.1" |
| 172 |
|
| 173 |
Encoding considerations: binary |
| 174 |
|
| 175 |
Security considerations: Application/mxf objects are not signed but |
| 176 |
may be partially encrypted internally. External security mechanisms |
| 177 |
must be employed to ensure content confidentiality. MXF, through |
| 178 |
metadata extensions, may allow executable code to be transferred in |
| 179 |
the file. It is suggested that no unauthenticated executables |
| 180 |
decoded from an MXF file be executed. Some compressed essence types |
| 181 |
carried in MXF may carry a risk that certain pathological bitstreams |
| 182 |
could lead to potential denial-of-service attacks against these |
| 183 |
essence decoders. |
| 184 |
|
| 185 |
Interoperability considerations: MXF provides a standard wrapping for |
| 186 |
a number of audio and video essence types according to a number of |
| 187 |
different Operational Patterns (OP). Thus, interoperability depends |
| 188 |
upon whether the MXF file decoder has the capability to match the |
| 189 |
features of the MXF file encoder. An Application Specification (AS) |
| 190 |
can ensure that MXF encoders and decoders can interoperate |
| 191 |
effectively. |
| 192 |
|
| 193 |
Published specification: <a href="./rfc4539">RFC 4539</a>, SMPTE 377M [<a href="#ref-SMPTE377M" title=""Material Exchange Format (MXF) File Format Specification"">SMPTE377M</a>] |
| 194 |
|
| 195 |
Applications that use this media type: MXF is a wrapper for many |
| 196 |
types of audio and video essence types in use by many applications in |
| 197 |
the broadcast and digital cinema industries. These include |
| 198 |
non-linear editing systems, video servers, video camera systems, |
| 199 |
digital asset management systems, and digital video distribution |
| 200 |
systems. |
| 201 |
|
| 202 |
Additional information: |
| 203 |
|
| 204 |
Magic number(s): none |
| 205 |
|
| 206 |
File extension(s): .mxf |
| 207 |
|
| 208 |
Macintosh File Type Code(s): "mxf " |
| 209 |
|
| 210 |
Person & email address to contact for further information: |
| 211 |
Thomas Edwards |
| 212 |
email: [email protected] |
| 213 |
|
| 214 |
Intended usage: COMMON |
| 215 |
|
| 216 |
Restrictions on usage: none |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Edwards Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc4539">RFC 4539</a> Media Type Registration for MXF May 2006</span> |
| 223 |
|
| 224 |
|
| 225 |
Author/Change controller: |
| 226 |
|
| 227 |
Thomas Edwards |
| 228 |
email: [email protected] |
| 229 |
|
| 230 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span> |
| 231 |
|
| 232 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Normative References</span> |
| 233 |
|
| 234 |
[<a id="ref-SMPTE377M">SMPTE377M</a>] Society of Motion Picture and Television Engineers, |
| 235 |
"Material Exchange Format (MXF) File Format |
| 236 |
Specification", SMPTE 377M-2004, <<a href="http://www.smpte.org">http://www.smpte.org</a>>. |
| 237 |
|
| 238 |
[<a id="ref-SMPTE400M">SMPTE400M</a>] Society of Motion Picture and Television Engineers, |
| 239 |
"SMPTE Labels Structure", SMPTE 400M-2004, |
| 240 |
<<a href="http://www.smpte.org">http://www.smpte.org</a>>. |
| 241 |
|
| 242 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Informative References</span> |
| 243 |
|
| 244 |
[<a id="ref-ASN1">ASN1</a>] International Telephone and Telegraph Consultative |
| 245 |
Committee, "Specification of Basic Encoding Rules for |
| 246 |
Abstract Syntax Notation One (ASN.1)", |
| 247 |
CCITT Recommendation X.209, January 1988. |
| 248 |
|
| 249 |
[<a id="ref-RFC2045">RFC2045</a>] Freed, N. and N. Borenstein, "Multipurpose Internet Mail |
| 250 |
Extensions (MIME) Part One: Format of Internet Message |
| 251 |
Bodies", <a href="./rfc2045">RFC 2045</a>, November 1996. |
| 252 |
|
| 253 |
[<a id="ref-RFC3061">RFC3061</a>] Mealling, M., "A URN Namespace of Object Identifiers", |
| 254 |
<a href="./rfc3061">RFC 3061</a>, February 2001. |
| 255 |
|
| 256 |
[<a id="ref-RFC4288">RFC4288</a>] Freed, N. and J. Klensin, "Media Type Specifications and |
| 257 |
Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="./rfc4288">RFC 4288</a>, December |
| 258 |
2005. |
| 259 |
|
| 260 |
Author's Address |
| 261 |
|
| 262 |
Thomas G. Edwards |
| 263 |
PBS |
| 264 |
6453 Stephenson Way |
| 265 |
Alexandria, VA 22312 |
| 266 |
US |
| 267 |
|
| 268 |
Phone: +1 703 739 5000 |
| 269 |
EMail: [email protected] |
| 270 |
URI: <a href="http://www.pbs.org">http://www.pbs.org</a> |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Edwards Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc4539">RFC 4539</a> Media Type Registration for MXF May 2006</span> |
| 279 |
|
| 280 |
|
| 281 |
Full Copyright Statement |
| 282 |
|
| 283 |
Copyright (C) The Internet Society (2006). |
| 284 |
|
| 285 |
This document is subject to the rights, licenses and restrictions |
| 286 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 287 |
retain all their rights. |
| 288 |
|
| 289 |
This document and the information contained herein are provided on an |
| 290 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 291 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
| 292 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
| 293 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
| 294 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 295 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 296 |
|
| 297 |
Intellectual Property |
| 298 |
|
| 299 |
The IETF takes no position regarding the validity or scope of any |
| 300 |
Intellectual Property Rights or other rights that might be claimed to |
| 301 |
pertain to the implementation or use of the technology described in |
| 302 |
this document or the extent to which any license under such rights |
| 303 |
might or might not be available; nor does it represent that it has |
| 304 |
made any independent effort to identify any such rights. Information |
| 305 |
on the procedures with respect to rights in RFC documents can be |
| 306 |
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>. |
| 307 |
|
| 308 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 309 |
assurances of licenses to be made available, or the result of an |
| 310 |
attempt made to obtain a general license or permission for the use of |
| 311 |
such proprietary rights by implementers or users of this |
| 312 |
specification can be obtained from the IETF on-line IPR repository at |
| 313 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 314 |
|
| 315 |
The IETF invites any interested party to bring to its attention any |
| 316 |
copyrights, patents or patent applications, or other proprietary |
| 317 |
rights that may cover technology that may be required to implement |
| 318 |
this standard. Please address the information to the IETF at |
| 319 |
[email protected]. |
| 320 |
|
| 321 |
Acknowledgement |
| 322 |
|
| 323 |
Funding for the RFC Editor function is provided by the IETF |
| 324 |
Administrative Support Activity (IASA). |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
Edwards Informational [Page 6] |
| 333 |
</pre> |