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
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
|
<pre>Internet Engineering Task Force (IETF) R. Gellens
Request for Comments: 6381 QUALCOMM, Inc.
Obsoletes: <a href="./rfc4281">4281</a> D. Singer
Updates: <a href="./rfc3839">3839</a>, <a href="./rfc4337">4337</a>, <a href="./rfc4393">4393</a> Apple, Inc.
Category: Standards Track P. Frojdh
ISSN: 2070-1721 Ericsson AB
August 2011
<span class="h1">The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types</span>
Abstract
Several MIME type/subtype combinations exist that can contain
different media formats. A receiving agent thus needs to examine the
details of such media content to determine if the specific elements
can be rendered given an available set of codecs. Especially when
the end system has limited resources, or the connection to the end
system has limited bandwidth, it is helpful to know from the Content-
Type alone if the content can be rendered.
This document specifies two parameters, 'codecs' and 'profiles', that
are used with various MIME types or type/subtype combinations to
allow for unambiguous specification of the codecs employed by the
media formats contained within, or the profile(s) of the overall
container format. This document obsoletes <a href="./rfc4281">RFC 4281</a>; <a href="./rfc4281">RFC 4281</a> defines
the 'codecs' parameter, which this document retains in a backwards
compatible manner with minor clarifications; the 'profiles' parameter
is added by this document.
By labeling content with the specific codecs indicated to render the
contained media, receiving systems can determine if the codecs are
supported by the end system, and if not, can take appropriate action
(such as rejecting the content, sending notification of the
situation, transcoding the content to a supported type, fetching and
installing the required codecs, further inspection to determine if it
will be sufficient to support a subset of the indicated codecs,
etc.).
Similarly, the profiles can provide an overall indication, to the
receiver, of the specifications with which the content complies.
This is an indication of the compatibility of the container format
and its contents to some specification. The receiver may be able to
work out the extent to which it can handle and render the content by
examining to see which of the declared profiles it supports, and what
they mean.
<span class="grey">Gellens, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6381">http://www.rfc-editor.org/info/rfc6381</a>.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Gellens, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Conventions Used in This Document ...............................<a href="#page-5">5</a>
<a href="#section-3">3</a>. The 'Codecs' Parameter ..........................................<a href="#page-5">5</a>
<a href="#section-3.1">3.1</a>. Introduction ...............................................<a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. Generic Syntax .............................................<a href="#page-7">7</a>
<a href="#section-3.3">3.3</a>. ISO Base Media File Format Name Space ......................<a href="#page-8">8</a>
<a href="#section-3.4">3.4</a>. ISO-Family Syntax .........................................<a href="#page-11">11</a>
<a href="#section-3.5">3.5</a>. Use in Additional Media Types .............................<a href="#page-11">11</a>
<a href="#section-3.6">3.6</a>. Examples ..................................................<a href="#page-12">12</a>
<a href="#section-3.7">3.7</a>. Additional Media Feature Details ..........................<a href="#page-12">12</a>
<a href="#section-4">4</a>. The 'Profiles' Parameter .......................................<a href="#page-12">12</a>
<a href="#section-4.1">4.1</a>. Introduction ..............................................<a href="#page-12">12</a>
<a href="#section-4.2">4.2</a>. Formal Declaration ........................................<a href="#page-13">13</a>
<a href="#section-4.3">4.3</a>. 'Profiles' Parameter Definition ...........................<a href="#page-14">14</a>
<a href="#section-4.4">4.4</a>. Profiles for Files Carrying MP4RA-Registered Brands .......<a href="#page-14">14</a>
<a href="#section-4.5">4.5</a>. 'Profiles' Parameter BNF Definition .......................<a href="#page-15">15</a>
<a href="#section-5">5</a>. IANA Considerations ............................................<a href="#page-15">15</a>
<a href="#section-6">6</a>. Registration ...................................................<a href="#page-15">15</a>
<a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-16">16</a>
<a href="#section-8">8</a>. Differences from <a href="./rfc4281">RFC 4281</a> ......................................<a href="#page-16">16</a>
<a href="#section-9">9</a>. Acknowledgements ...............................................<a href="#page-17">17</a>
<a href="#section-10">10</a>. References ....................................................<a href="#page-17">17</a>
<a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-17">17</a>
<a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-18">18</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
One of the original motivations for MIME is the ability to identify
the specific media type of a message part. However, due to various
factors, it is not always possible from looking at the MIME type and
subtype to know which specific media formats are contained in the
body part or which codecs are indicated in order to render the
content.
There are several media type/subtypes (either currently registered or
deployed with registration pending) that contain codecs chosen from a
set. In the absence of the parameters described here, it is
necessary to examine each media element in order to determine the
codecs or other features required to render the content. For
example, video/3gpp may contain any of the video formats H.263
Profile 0, H.263 Profile 3, H.264, MPEG-4 Simple Profile, and/or any
of the audio formats Adaptive Multi Rate (AMR), Adaptive Multi Rate -
WideBand (AMR-WB), Extended AMR-WB, Advanced Audio Coding (AAC), or
Enhanced aacPlus, as specified in [<a href="#ref-3GPP-Formats" title=""Technical Specification Group Services and System Aspects; Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)"">3GPP-Formats</a>].
<span class="grey">Gellens, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
In some cases, the specific codecs can be determined by examining the
header information of the media content. While this isn't as bad as
examining the entire content, it still requires specialized knowledge
of each format and is resource consumptive.
This ambiguity can be a problem for various clients and servers. For
example, it presents a significant burden to Multimedia Messaging
(MMS) servers, which must examine the media sent in each message in
order to determine which codecs are required to render the content.
Only then can such a server determine if the content requires
transcoding or specialized handling prior to being transmitted to the
handset.
Additionally, it presents a challenge to smart clients on devices
with constrained memory, processing power, or transmission bandwidth
(such as cellular telephones and PDAs). Such clients often need to
determine in advance if they are currently capable of rendering the
content contained in an MMS or email message.
Ambiguity:
o audio/3gpp can contain AMR, AAC, AMR-WB, Extended AMR-WB, or
Enhanced aacPlus contents as specified in [<a href="#ref-3GPP-Formats" title=""Technical Specification Group Services and System Aspects; Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)"">3GPP-Formats</a>].
o audio/3gpp2 can contain AMR, AAC, 13K (as per [<a href="./rfc3625" title=""The QCP File Format and Media Types for Speech Data"">RFC3625</a>]), Enhanced
Variable Rate Codec (EVRC), Selectable Mode Vocoder (SMV), or
Variable Multi Rate WideBand (VMR-WB), as specified in
[<a href="#ref-3GPP2-Formats" title=""3GPP2 File Formats for Multimedia Service"">3GPP2-Formats</a>].
o video/3gpp can contain H.263 Profile 0, H.263 Profile 3, H.264,
MPEG-4 Simple Profile, and/or AMR, AMR-WB, Extended AMR-WB, AAC,
or Enhanced aacPlus, as specified in [<a href="#ref-3GPP-Formats" title=""Technical Specification Group Services and System Aspects; Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)"">3GPP-Formats</a>].
o video/3gpp2 can contain H.263 Profile 0, H.263 Profile 3, H.264,
MPEG-4 Simple Profile, and/or AMR, AAC, 13K (as per [<a href="./rfc3625" title=""The QCP File Format and Media Types for Speech Data"">RFC3625</a>]),
EVRC, SMV, or VMR-WB, as specified in [<a href="#ref-3GPP2-Formats" title=""3GPP2 File Formats for Multimedia Service"">3GPP2-Formats</a>].
o audio/mp4 can include any codec defined in MPEG-1, MPEG-2, MPEG-4
or registered at the MP4 registration authority [<a href="#ref-MP4RA" title=""MP4REG, The MPEG-4 Registration Authority"">MP4RA</a>].
o video/mp4 has the same issues as audio/mp4, and in addition many
video codecs, and especially the MPEG codecs, have a variety of
profiles and levels, not all of which are supported by every
implementation.
<span class="grey">Gellens, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
Note that there are additional media types that are ambiguous, but
are outside the scope of this document, including:
o video/mpeg4-generic, which can contain anything allowed by the
MPEG-4 specification, or any codec registered with the MP4
registration authority [<a href="#ref-MP4RA" title=""MP4REG, The MPEG-4 Registration Authority"">MP4RA</a>];
With each "bucket" type, a receiving agent only knows that it has a
container format. It doesn't even know whether content that is
labeled video/3gpp or video/3gpp2 contains video; it might be audio
only, audio and video, or video only.
A solution that permits a receiving agent to determine the specific
codecs or profiles required to render media content would help
provide efficient and scalable servers, especially for Multimedia
Messaging (MMS), and aid the growth of multimedia services in
wireless networks.
<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 "Key words for use in
RFCs to Indicate Requirement Levels" [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] .
The syntax in this document uses the BNF rules specified in [<a href="./rfc2045" title=""Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"">RFC2045</a>]
and [<a href="./rfc2231" title=""MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"">RFC2231</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The 'Codecs' Parameter</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Introduction</span>
This section adds a parameter to allow unambiguous specification of
all codecs indicated to render the content in the MIME part. This
parameter is optional in all current types to which it is added.
Future types that contain ambiguity are strongly encouraged to
include this parameter.
This parameter applies to:
1. Files in the family based on the ISO Base Media File Format
[<a href="#ref-ISO14496-12" title=""Information technology -- Coding of audio-visual objects -- Part 12: ISO base media file format"">ISO14496-12</a>] called "ISO family files" in this specification.
2. The QuickTime file format, owned by Apple, Inc.
This includes the media types:
1. audio/3gpp, video/3gpp [<a href="./rfc3839" title=""MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files"">RFC3839</a>]
<span class="grey">Gellens, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
2. audio/3gpp2, video/3gpp2 [<a href="./rfc4393" title=""MIME Type Registrations for 3GPP2 Multimedia Files"">RFC4393</a>]
3. audio/mp4, video/mp4, application/mp4 [<a href="./rfc4337" title=""MIME Type Registration for MPEG-4"">RFC4337</a>]
4. video/quicktime
5. application/mp21 (see note below)
Note that MPEG-21 files under the type application/mp21 may, but are
not required to, contain a top-level 'moov' atom providing a timed,
coded, resource. The 'codecs' parameter SHOULD only be used for
MPEG-21 files when this timed material is also present in the file.
Parameter name: codecs
Parameter value: A single value, or a comma-separated list of values
identifying the codec(s) indicated to render the content in the body
part.
Each value consists of one or more dot-separated elements. The name
space for the first element is determined by the MIME type. The name
space for each subsequent element is determined by the preceding
element. The precise syntax is given below in the Generic Syntax
(<a href="#section-3.2">Section 3.2</a>).
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
to separate multiple values) require that the entire parameter value
be enclosed in quotes.
An element MAY include an octet that [<a href="./rfc2045" title=""Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"">RFC2045</a>] requires encoding. In
this case, [<a href="./rfc2231" title=""MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"">RFC2231</a>] is used: an asterisk ("*") is placed at the end
of the parameter name (becoming 'codecs*' instead of 'codecs'), the
parameter value usually starts with two single quote ("'") characters
(indicating that neither character set nor language is specified),
and each octet that requires encoding is represented as a percent
sign ("%") followed by two hexadecimal digits. Note that, when the
[<a href="./rfc2231" title=""MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"">RFC2231</a>] form is used, the percent sign, asterisk, and single quote
characters have special meaning and so MUST themselves be percent
encoded.
Examples of Generic Syntax:
codecs=a.bb.ccc.d
codecs="a.bb.ccc.d, e.fff"
codecs*=''fo%2e
codecs*="''%25%20xz, gork"
<span class="grey">Gellens, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
When the 'codecs' parameter is used, it MUST contain all codecs
indicated by the content present in the body part. The 'codecs'
parameter MUST NOT include any codecs that are not indicated by any
media elements in the body part.
In some cases, not all indicated codecs are absolutely required in
order to render the content. Therefore, when a receiver does not
support all listed codecs, special handling might be required. For
example, the media element(s) could be examined in order to determine
if an unsupported codec is actually required (e.g., there may be
alternative tracks (such as English and Spanish audio), there may be
timed text that can be dropped, etc.).
Although the encoder MUST create parameter values that are complete
and accurate in 'breadth' (that is, the encoder MUST report all four-
character codes used in all tracks for ISO family files, for example)
receivers MUST NOT rely on the parameter values being complete in
'depth'. (If the hierarchical rules for a given code (e.g., 'qvxy')
were written after a server was implemented, for example, that server
would not know what elements to place after 'qvxy').
Although a mismatch is not permitted by this specification, the body
part is definitive of the actual codecs needed; the parameter
supplied here is informative. If a receiver encounters a body part
whose 'codecs' parameter contains codecs that are not indicated by
any media elements, then the receiver SHOULD process the body part by
discarding the information in the 'codecs' parameter.
If a receiver encounters a body part whose 'codecs' parameter does
not contain all codecs indicated by the media elements, then the
receiver MAY process the body part by discarding the information in
the 'codecs' parameter.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Generic Syntax</span>
The 'codecs' parameter takes either of two forms. The first form is
used when the value does not contain any octets that require
encoding. The second form uses [<a href="./rfc2231" title=""MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"">RFC2231</a>] to allow arbitrary octets
to be encoded. With either form, quotes allow for commas and other
characters in <tspecials> (quotes MAY be used even when not
required).
This BNF uses the rules specified in [<a href="./rfc2045" title=""Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"">RFC2045</a>] and [<a href="./rfc2231" title=""MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"">RFC2231</a>].
While [<a href="./rfc2231" title=""MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"">RFC2231</a>] allows specification of character set and language,
this parameter does not contain items intended for human consumption,
and hence makes no use of language. The language element SHOULD be
<span class="grey">Gellens, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
omitted; the character set SHOULD also be omitted. A receiver MAY
ignore language and MAY choose to support only US-ASCII [<a href="./rfc1345" title=""Character Mnemonics and Character Sets"">RFC1345</a>] and
UTF-8 [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>].
Implementations MUST NOT add comments and/or folding white space
(CFWS) between the tokens except after ",". TOKEN is defined in
[<a href="./rfc2045" title=""Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"">RFC2045</a>], and <ext-octet> and <attribute-char> are defined in
[<a href="./rfc2231" title=""MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"">RFC2231</a>].
The BNF syntax is as follows:
codecs := cod-simple / cod-fancy
cod-simple := "codecs" "=" unencodedv
unencodedv := id-simple / simp-list
simp-list := DQUOTE id-simple *( "," id-simple ) DQUOTE
id-simple := element
; "." reserved as hierarchy delimiter
element := 1*octet-sim
octet-sim := <any TOKEN character>
; Within a 'codecs' parameter value, "." is reserved
; as a hierarchy delimiter
cod-fancy := "codecs*" "=" encodedv
encodedv := fancy-sing / fancy-list
fancy-sing := [charset] "'" [language] "'" id-encoded
; Parsers MAY ignore <language>
; Parsers MAY support only US-ASCII and UTF-8
fancy-list := DQUOTE [charset] "'" [language] "'" id-list DQUOTE
; Parsers MAY ignore <language>
; Parsers MAY support only US-ASCII and UTF-8
id-list := id-encoded *( "," id-encoded )
id-encoded := encoded-elm *( "." encoded-elm )
; "." reserved as hierarchy delimiter
encoded-elm := 1*octet-fancy
octet-fancy := ext-octet / attribute-char
DQUOTE := %x22 ; " (double quote)
Initial name space: This document only defines values for files in
the ISO Base Media File Format and QuickTime families. Other file
formats may also define codec naming.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. ISO Base Media File Format Name Space</span>
For the ISO Base Media File Format, and the QuickTime movie file
format, the first element of a 'codecs' parameter value is a sample
description entry four-character code as registered by the MP4
Registration Authority [<a href="#ref-MP4RA" title=""MP4REG, The MPEG-4 Registration Authority"">MP4RA</a>]. Values are case sensitive.
<span class="grey">Gellens, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
Note that there are potentially multiple tracks in a file, each
potentially carrying multiple sample entries (some but not all uses
of the ISO Base Media File Format restrict the number of sample
entries in a track to one).
When the first element of a value is 'mp4a' (indicating some kind of
MPEG-4 audio), or 'mp4v' (indicating some kind of MPEG-4 part-2
video), or 'mp4s' (indicating some kind of MPEG-4 Systems streams
such as MPEG-4 BInary Format for Scenes (BIFS)), the second element
is the hexadecimal representation of the MP4 Registration Authority
ObjectTypeIndication (OTI), as specified in [<a href="#ref-MP4RA" title=""MP4REG, The MPEG-4 Registration Authority"">MP4RA</a>] and [<a href="#ref-MP41" title=""Information technology--Coding of audio-visual objects -- Part 1: Systems"">MP41</a>]
(including amendments). Note that [<a href="#ref-MP4RA" title=""MP4REG, The MPEG-4 Registration Authority"">MP4RA</a>] uses a leading "0x" with
these values, which is omitted here and hence implied.
One of the OTI values for 'mp4a' is 40 (identifying MPEG-4 audio).
For this value, the third element identifies the audio
ObjectTypeIndication (OTI) as defined in [<a href="#ref-MP4A" title=""Information technology--Coding of audio-visual objects -- 3: Audio"">MP4A</a>] (including
amendments), expressed as a decimal number.
For example, AAC low complexity (AAC-LC) has the value 2, so a
complete string for AAC-LC would be "mp4a.40.2".
One of the OTI values for 'mp4v' is 20 (identifying MPEG-4 part-2
video). For this value, the third element identifies the video
ProfileLevelIndication as defined in [<a href="#ref-MP4V" title=""Information technology--Coding of audio-visual objects -- Part 2: Visual"">MP4V</a>] (including amendments),
expressed as a decimal number.
For example, MPEG-4 Visual Simple Profile Level 0 has the value 9, so
a complete string for MPEG-4 Visual Simple Profile Level 0 would be
"mp4v.20.9".
When the first element of a value is a code indicating a codec from
the Advanced Video Coding specification [<a href="#ref-AVC" title=""Advanced video coding for generic audiovisual services"">AVC</a>], specifically one of
the sample entries defined in [<a href="#ref-AVC-Formats" title=""Information technology -- Coding of audio-visual objects -- Part 15: Advanced Video Coding (AVC) file format"">AVC-Formats</a>] (such as 'avc1', 'avc2',
'svc1', 'mvc1', and 'mvc2') -- indicating AVC (H.264), Scalable Video
Coding (SVC), or Multiview Video Coding (MVC), the second element
(referred to as 'avcoti' in the formal syntax) is the hexadecimal
representation of the following three bytes in the (subset) sequence
parameter set Network Abstraction Layer (NAL) unit specified in
[<a href="#ref-AVC" title=""Advanced video coding for generic audiovisual services"">AVC</a>]:
(1) profile_idc,
(2) the byte containing the constraint_set flags (currently
constraint_set0_flag through constraint_set5_flag, and the
reserved_zero_2bits), and
(3) level_idc.
<span class="grey">Gellens, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
Note that the sample entries 'avc1' and 'avc2' do not necessarily
indicate that the media only contains AVC NAL units. In fact, the
media may be encoded as an SVC or MVC profile and thus contain SVC or
MVC NAL units. In order to be able to determine which codec is used,
further information is necessary (profile_idc). Note also that
reserved_zero_2bits is required to be equal to 0 in [<a href="#ref-AVC" title=""Advanced video coding for generic audiovisual services"">AVC</a>], but other
values for it may be specified in the future by ITU-T or ISO/IEC.
This is as previously defined in the 3GPP File Format specification
3GPP TS 26.244 [<a href="#ref-3GPP-Formats" title=""Technical Specification Group Services and System Aspects; Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)"">3GPP-Formats</a>], Section A.2.2.
When SVC or MVC content is coded in an AVC-compatible fashion, the
sample description may include both an AVC configuration record and
an SVC or MVC configuration record. Under those circumstances, it is
recommended that the two configuration records both be reported as
they may contain different AVC profile, level, and compatibility
indicator values. Thus, the codecs reported would include the sample
description code (e.g., 'avc1') twice, with the values from one of
the configuration records forming the 'avcoti' information in each.
<span class="grey">Gellens, et al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. ISO-Family Syntax</span>
id-simple :=/ id-iso
id-encoded :=/ id-iso
id-iso := iso-gen / iso-mpega / iso-mpegv / iso-avc
iso-gen := cpid *( element / encoded-elm )
; <element> used with <codecs-simple>
; <encoded-elm> used with <codecs-fancy>
;
; Note that the BNF permits "." within <element>
; and <encoded-elm> but "." is reserved as the
; hierarchy delimiter
iso-mpega := mp4a "." oti [ "." aud-oti ]
iso-mpegv := mp4v "." oti [ "." vid-pli ]
iso-avc := avc1 / avc2 / svc1 / mvc1 / mvc2 [ "." avcoti ]
cpid := 4(octet-simple / octet-fancy)
; <octet-simple> used with <codecs-simple>
; <octet-fancy> used with <codecs-fancy>
mp4a := %x6d.70.34.61 ; 'mp4a'
oti := 2(DIGIT / "A" / "B" / "C" / "D" / "E" / "F")
; leading "0x" omitted
avc1 := %x61.76.63.31 ; 'avc1'
avc2 := %x61.76.63.32 ; 'avc2'
svc1 := %x73.76.63.31 ; 'svc1'
mvc1 := %x6d.76.63.31 ; 'mvc1'
mvc2 := %x6d.76.63.32 ; 'mvc2'
avcoti := 6(DIGIT / "A" / "B" / "C" / "D" / "E" / "F")
; leading "0x" omitted
aud-oti := 1*DIGIT
mp4v := %x6d.70.34.76 ; 'mp4v'
vid-pli := 1*DIGIT
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Use in Additional Media Types</span>
This parameter MAY be specified for use with additional MIME media
types.
For ISO family file formats where the name space as defined here is
sufficient, all that needs to be done is to update the media type
registration to specify the 'codecs' parameter with a reference to
this document. For existing media types, it is generally advisable
for the parameter to be optional; for new media types, the parameter
MAY be optional or required, as appropriate.
For ISO family file formats where the name space as defined here
needs to be expanded, a new document MAY update this one by
specifying the additional detail.
<span class="grey">Gellens, et al. Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
For non-ISO family file formats, a new document MAY update this one
by specifying the name space for the media type(s).
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Examples</span>
Content-Type: video/3gpp2; codecs="sevc, s263"
(EVRC audio plus H.263 video)
Content-Type: audio/3gpp; codecs=samr
(AMR audio)
Content-Type: video/3gpp; codecs="s263, samr"
(H.263 video plus AMR audio)
Content-Type: audio/3gpp2; codecs=mp4a.E1
(13K audio)
Content-Type: video/3gpp2; codecs="mp4v.20.9, mp4a.E1"
(MPEG-4 Visual Simple Profile Level 0 plus 13K voice)
Content-Type: video/mp4; codecs="avc1.640028"
(H.264/AVC video, High Profile, Level 40,
e.g., DVB 720p 50Hz HDTV)
Content-Type: video/mp4; codecs="svc1.56401E, avc1.4D401E"
(SVC video, Scalable High Profile, Level 30,
with a Main Profile AVC base layer, e.g., DVB 25 Hz SDTV)
Content-Type: video/mp4; codecs="mvc1.800030, avc1.640030"
(MVC video, Stereo High Profile, Level 42,
with a High Profile base layer, e.g., as adopted in Blu-ray)
Note: OTI value 20 ("0x20" in [<a href="#ref-MP4RA" title=""MP4REG, The MPEG-4 Registration Authority"">MP4RA</a>]) says "Includes associated
Amendment(s) and Corrigendum(a). The actual object types are defined
in [<a href="#ref-MP4V" title=""Information technology--Coding of audio-visual objects -- Part 2: Visual"">MP4V</a>] and are conveyed in the DecoderSpecificInfo as specified in
[<a href="#ref-MP4V" title=""Information technology--Coding of audio-visual objects -- Part 2: Visual"">MP4V</a>], Annex K." (references adjusted).
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. Additional Media Feature Details</span>
It is sometimes helpful to provide additional details for a media
element (e.g., the number of X and Y pixels, the color depth, etc.).
These details are sometimes called "media features" or "media
characteristics".
When such additional features are included, the content-features
[<a href="./rfc2912" title=""Indicating Media Features for MIME Content"">RFC2912</a>] header provides a handy way to do so.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. The 'Profiles' Parameter</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Introduction</span>
Just as some codecs have a variety of profiles (subsets of their
functionality within which a bitstream can be coded), some media
files can also be profiled and be associated with one or more profile
identifiers of the profiles to which they conform. These profiles
<span class="grey">Gellens, et al. Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
can indicate features of the file format itself, which codecs may be
present, the profiles of those codecs, and so on. It can be
advantageous to a receiving system to know the overall file
profile(s) of a file; indeed, under these circumstances it may not be
necessary to know the codecs themselves if they are implied by the
profile.
The 'profiles' parameter reports on the profile(s) of the overall
container format. A profile of the container format may have
restrictions on not only the features of the container format itself
but also on what codecs may be included, and it may indeed have
restrictions on the profiles of those codecs. The 'profiles'
parameter does not, however, report directly any profiles of the
contained media: when such codec-specific profiles are reported, this
report is part of the 'codecs' parameter. The 'profiles' parameter
reports only the profile(s) applying to the complete container.
When the use of the 'profiles' parameter is defined for a given
format, that definition SHOULD indicate that it directly reflects
information in the body part, i.e., that it does not convey
information beyond, or different from, what can be learnt by
inspecting the body part. Although a mismatch is not permitted by
this specification, the body part is definitive of the actual
profiles; the parameter supplied here is informative.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Formal Declaration</span>
This section adds a parameter to allow unambiguous specification of
the profiles to which a file claims conformance. This parameter is
OPTIONAL in all current types to which it is added.
This parameter applies to Box-structured (also known as atom-
structured) files that have an initial box containing compatibility
brands, as registered at the MP4 Registration Authority [<a href="#ref-MP4RA" title=""MP4REG, The MPEG-4 Registration Authority"">MP4RA</a>], such
as a filetype or segment-type box. Principally, this includes files
in the family based on the ISO Base Media File Format [<a href="#ref-ISO14496-12" title=""Information technology -- Coding of audio-visual objects -- Part 12: ISO base media file format"">ISO14496-12</a>]
and the QuickTime file format, owned by Apple, Inc. (A brand can
indicate conformance with restrictions regarding which codecs and
file format features are used, adherence to quantitative limits such
as the length/size of the file, and so on.)
This includes the media types:
1. audio/3gpp, video/3gpp [<a href="./rfc3839" title=""MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files"">RFC3839</a>]
2. audio/3gpp2, video/3gpp2 [<a href="./rfc4393" title=""MIME Type Registrations for 3GPP2 Multimedia Files"">RFC4393</a>]
3. audio/mp4, video/mp4 [<a href="./rfc4337" title=""MIME Type Registration for MPEG-4"">RFC4337</a>]
<span class="grey">Gellens, et al. Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
4. video/quicktime
5. application/mp21
Parameter name: profiles
Parameter value: A single value, or a comma-separated list of values
identifying the profiles(s) to which the file claims conformance.
The name space is determined by the MIME type.
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
to separate multiple values) require that the entire parameter value
be enclosed in quotes.
An element MAY include an octet that [<a href="./rfc2045" title=""Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"">RFC2045</a>] requires encoding. In
this case, [<a href="./rfc2231" title=""MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"">RFC2231</a>] is used: an asterisk ("*") is placed at the end
of the parameter name (becoming 'profiles*' instead of 'profiles'),
the parameter value usually starts with two single quote ("'")
characters(indicating that neither character set nor language is
specified), and each octet that requires encoding is represented as a
percent sign ("%") followed by two hexadecimal digits. Note that,
when the [<a href="./rfc2231" title=""MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations"">RFC2231</a>] form is used, the percent sign, asterisk, and
single quote characters have special meaning and so MUST themselves
be percent encoded.
Examples of Generic Syntax:
profiles="isom,mp41,qvXt"
profiles*="''%25%20xz, gork"
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. 'Profiles' Parameter Definition</span>
The 'profiles' parameter is an OPTIONAL parameter that indicates one
or more profiles to which the file claims conformance. Like the
'codecs' parameter described above, it may occur as either 'profiles'
or 'profiles*', with the same encoding rules. The value is, as for
the 'codecs' parameter, a comma-separated list of profile
identifiers.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Profiles for Files Carrying MP4RA-Registered Brands</span>
For any file format carrying a brand registered at the MP4
Registration Authority [<a href="#ref-MP4RA" title=""MP4REG, The MPEG-4 Registration Authority"">MP4RA</a>], notably files based on the ISO Base
Media File Format ISO/IEC 14496-12 [<a href="#ref-ISO14496-12" title=""Information technology -- Coding of audio-visual objects -- Part 12: ISO base media file format"">ISO14496-12</a>] and QuickTime movie
files, the 'profiles' parameter MUST list exactly the major-brand,
followed by the compatible-brands, as listed in the filetype box
('ftyp') or segment-type box ('styp'). The major-brand MUST be
first, and MAY be removed from the compatible-brands list. (The file
<span class="grey">Gellens, et al. Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
format requires that it be repeated in the compatible-brands, but
this requirement is relaxed here for compactness.)
An example might be profiles="mp41,isom,qvXt", indicating that MPEG-4
version 1 is the major-brand and preferred use, that the file is
compatible with the version of the base file format identified by
'isom', and that it is also compatible with the specification/profile
'qvXt' (whatever that may be).
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. 'Profiles' Parameter BNF Definition</span>
profiles := pro-simple / pro-fancy
pro-simple := "profiles" "=" unencodedv
pro-fancy := "profiles*" "=" encodedv
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has replaced references to [<a href="./rfc4281" title=""The Codecs Parameter for "">RFC4281</a>] with references to this
document in the "MIME Media Types" registry, thereby indicating that
the 'codecs' and/or 'profiles' parameters are optional for the
following media types (as listed in Sections <a href="#section-3">3</a> and <a href="#section-4">4</a>):
1. audio/3gpp, video/3gpp [<a href="./rfc3839" title=""MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files"">RFC3839</a>]
2. audio/3gpp2, video/3gpp2 [<a href="./rfc4393" title=""MIME Type Registrations for 3GPP2 Multimedia Files"">RFC4393</a>]
3. audio/mp4, video/mp4, application/mp4 [<a href="./rfc4337" title=""MIME Type Registration for MPEG-4"">RFC4337</a>]
4. video/quicktime
5. application/mp21
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Registration</span>
The MPEG4 Registration Authority can be consulted for the most up-to-
date registration of sub-parameters for the codecs type, for specific
codecs.
<span class="grey">Gellens, et al. Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
The 'codecs' parameter itself does not alter the security
considerations of any of the media types with which it is used. Each
audio and video media type has its own set of security considerations
that continue to apply, regardless of the use of the 'codecs'
parameter.
An incorrect 'codecs' parameter might cause media content to be
received by a device that is not capable of rendering it or might
cause media content not to be sent to a device that is capable of
receiving it. An incorrect 'codecs' parameter is therefore capable
of some types of denial-of-service attacks. However, this is most
likely to arise by accident, as an attacker capable of altering media
data in transit could cause more harm by altering the media format
itself, or even the content type header, rather than just the
'codecs' parameter of the content type header.
To the extent that a receiver reacts to a 'codecs' parameter that
indicates an unsupported codec, by fetching and installing the
required codecs, such reaction needs to be performed carefully and in
accord with the system's normal validity and security checks and
procedures.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Differences from <a href="./rfc4281">RFC 4281</a></span>
1. Improved the introduction and other supporting and explanatory
text;
2. improved the references;
3. clarified the MIME types to which the parameters apply, and
clarified the consequent IANA actions;
4. added the 'profiles' parameter;
5. fixed an error in the BNF, where it did not correspond to either
the examples or common usage;
6. added the definition of the sub-parameters for the AVC family of
codecs;
7. added a security consideration for possible triggering of
downloads;
8. updated acknowledgments.
<span class="grey">Gellens, et al. Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
Harinath Garudadri provided a great deal of help, which is very much
appreciated. Mary Barnes and Bruce Lilly provided detailed and
helpful comments. Reviews and comments by Sam Hartman, Russ Housley,
and Bert Wijnen were much appreciated. Chris Newman carefully
reviewed and improved the BNF.
Christian Timmerer helped with the MPEG-21 material, and Thomas
Schierl and Yago Sanchez helped with SVC and MVC.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
[<a id="ref-3GPP-Formats">3GPP-Formats</a>] 3rd Generation Partnership Project, "Technical
Specification Group Services and System Aspects;
Transparent end-to-end packet switched streaming
service (PSS); 3GPP file format (3GP)", 3GPP
TS 26.244.
[<a id="ref-AVC">AVC</a>] "Advanced video coding for generic audiovisual
services", ITU-T Recommendation H.264, ISO/
IEC 14496-10:2009.
[<a id="ref-AVC-Formats">AVC-Formats</a>] "Information technology -- Coding of audio-visual
objects -- Part 15: Advanced Video Coding (AVC) file
format", ISO/IEC 14496-15:2010.
[<a id="ref-ISO14496-12">ISO14496-12</a>] "Information technology -- Coding of audio-visual
objects -- Part 12: ISO base media file format",
ISO/IEC 14496-12:2008.
[<a id="ref-MP4RA">MP4RA</a>] "MP4REG, The MPEG-4 Registration Authority",
<<a href="http://www.mp4ra.org">http://www.mp4ra.org</a>>.
[<a id="ref-RFC2045">RFC2045</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-RFC2119">RFC2119</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-RFC2231">RFC2231</a>] Freed, N. and K. Moore, "MIME Parameter Value and
Encoded Word Extensions:
Character Sets, Languages, and Continuations",
<a href="./rfc2231">RFC 2231</a>, November 1997.
<span class="grey">Gellens, et al. Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
[<a id="ref-RFC2912">RFC2912</a>] Klyne, G., "Indicating Media Features for MIME
Content", <a href="./rfc2912">RFC 2912</a>, September 2000.
[<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003.
[<a id="ref-RFC3839">RFC3839</a>] Castagno, R. and D. Singer, "MIME Type Registrations
for 3rd Generation Partnership Project (3GPP)
Multimedia files", <a href="./rfc3839">RFC 3839</a>, July 2004.
[<a id="ref-RFC4281">RFC4281</a>] Gellens, R., Singer, D., and P. Frojdh, "The Codecs
Parameter for "Bucket" Media Types", <a href="./rfc4281">RFC 4281</a>,
November 2005.
[<a id="ref-RFC4337">RFC4337</a>] Y Lim and D. Singer, "MIME Type Registration for
MPEG-4", <a href="./rfc4337">RFC 4337</a>, March 2006.
[<a id="ref-RFC4393">RFC4393</a>] Garudadri, H., "MIME Type Registrations for 3GPP2
Multimedia Files", <a href="./rfc4393">RFC 4393</a>, March 2006.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-3GPP2-Formats">3GPP2-Formats</a>] Third Generation Partnership Project 2, "3GPP2 File
Formats for Multimedia Service", <<a href="http://www.3gpp2.org/Public_html/specs/C.S0050-0_v1.0_121503.pdf">http://</a>
<a href="http://www.3gpp2.org/Public_html/specs/C.S0050-0_v1.0_121503.pdf">www.3gpp2.org/Public_html/specs/</a>
<a href="http://www.3gpp2.org/Public_html/specs/C.S0050-0_v1.0_121503.pdf">C.S0050-0_v1.0_121503.pdf</a>>.
[<a id="ref-MP41">MP41</a>] "Information technology--Coding of audio-visual
objects -- Part 1: Systems", ISO/IEC 14496-1:2010.
[<a id="ref-MP4A">MP4A</a>] "Information technology--Coding of audio-visual
objects -- 3: Audio", ISO/IEC 14496-3:2009.
[<a id="ref-MP4V">MP4V</a>] "Information technology--Coding of audio-visual
objects -- Part 2: Visual", ISO/IEC 14496-2:2004.
[<a id="ref-RFC1345">RFC1345</a>] Simonsen, K., "Character Mnemonics and Character
Sets", <a href="./rfc1345">RFC 1345</a>, June 1992.
[<a id="ref-RFC3625">RFC3625</a>] Gellens, R. and H. Garudadri, "The QCP File Format
and Media Types for Speech Data", <a href="./rfc3625">RFC 3625</a>,
September 2003.
<span class="grey">Gellens, et al. Standards Track [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc6381">RFC 6381</a> MIME Codecs and Profiles August 2011</span>
Authors' Addresses
Randall Gellens
QUALCOMM Incorporated
5775 Morehouse Drive
San Diego, CA 92121
US
EMail: rg+ietf@qualcomm.com
David Singer
Apple, Inc.
1 Infinite Loop
Cupertino, CA 95014
US
Phone: +1 408 996 1010
EMail: singer@apple.com
Per Frojdh
Ericsson AB
Ericsson Research
Stockholm SE-164 80
Sweden
Phone: +46 10 7190000
EMail: Per.Frojdh@ericsson.com
Gellens, et al. Standards Track [Page 19]
</pre>
|
