AV1 Codec ISO Media File Format Binding


AOM Final Deliverable,

This version:
Previously approved version:
Latest approved version:
Latest draft version:
Test Suite:
Issue Tracking:
Cyril Concolato (Netflix)
Dimitri Podborski (Apple)
Wan-Teh Chang (Google)

Copyright 2024, AOM

Licensing information is available at http://aomedia.org/license/

The MATERIALS ARE PROVIDED “AS IS.” The Alliance for Open Media, its members, and its contributors expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to the materials. The entire risk as to implementing or otherwise using the materials is assumed by the implementer and user. IN NO EVENT WILL THE ALLIANCE FOR OPEN MEDIA, ITS MEMBERS, OR CONTRIBUTORS BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THIS DELIVERABLE OR ITS GOVERNING AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER MEMBER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


This document specifies the storage format for [AV1] bitstreams in [ISOBMFF] tracks as well as in [CMAF] files.

1. Bitstream features overview

An AV1 bitstream is composed of a sequence of OBUs, grouped into Temporal Units.

OBUs are made of a 1 or 2 bytes header, identifying in particular the type of OBU, followed by an optional length field and by an optional payload, whose presence and content depend on the OBU type. Depending on its type, an OBU can carry configuration information, metadata, or coded video data.

NOTE: Tile List OBUs defined in the [AV1] specification are not supported in the current version of this specification. A future version of the specification may do so.

Temporal Units are processed by a decoder in the order given by the bitstream. Each Temporal Unit is associated with a presentation time. Some Temporal Units may contain multiple frames to be decoded but only one is presented.

NOTE: The AV1 specification defines scalability features, allowing frames from multiple layers or operating points to be present in a single temporal unit. This version of storage in ISOBMFF supports the simple storage of scalable streams in a single track, but does not specify advanced tools for handling multi-track support, layer extraction, or other scalability related use cases. A future version of the specification may do so.

Frames carried in Temporal Units may have coding dependencies on frames carried previously in the same Temporal Unit or in previous Temporal Units. Frames that can be decoded without dependencies to previous frames are of two categories: Key Frames and Intra-only Frames. Frames that cannot be decoded independently are of three categories: Inter Frames, Switch Frames, and frames with a show_existing_frame flag set to 1.

Key Frames with the show_frame flag set to 1 have the additional property that after decoding the Key Frame, all frames following the Key Frame in the bitstream can be decoded. They are called Random Access Points in [AV1].

Key Frames with the show_frame flag set to 0 are called Delayed Random Access Points. Delayed Random Access Points have the additional property that if a future Key Frame Dependent Recovery Point exists, all frames following that Key Frame Dependent Recovery Point can be decoded. A Key Frame Dependent Recovery Point is a frame with show_existing_frame set to 1 that refers to a previous Delayed Random Access Points.

2. Basic Encapsulation Scheme

This section describes the basic data structures used to signal encapsulation of AV1 bitstreams in [ISOBMFF] containers.

2.1. General Requirements & Brands

A file conformant to this specification satisfies the following:

Parsers SHALL support the structures required by the iso6 brand and MAY support structures required by further ISOBMFF structural brands.

2.2. AV1 Sample Entry

2.2.1. Definition

Sample Entry Type: av01
Container:         Sample Description Box ('stsd')
Mandatory:         Yes 
Quantity:          One or more 

2.2.2. Description

The AV1SampleEntry sample entry identifies that the track contains AV1 Samples, and uses an AV1CodecConfigurationBox.

2.2.3. Syntax

class AV1SampleEntry
extends VisualSampleEntry('av01')
  AV1CodecConfigurationBox config;

2.2.4. Semantics

The width and height fields of the VisualSampleEntry SHALL equal the values of max_frame_width_minus_1 + 1 and max_frame_height_minus_1 + 1 of the Sequence Header OBU applying to the samples associated with this sample entry.

Let MaxRenderWidth be the maximum RenderWidth and MaxRenderHeight be the maximum RenderHeight of all the frames in the track.

The width and height in the TrackHeaderBox SHOULD be equal to MaxRenderWidth and MaxRenderHeight, respectively. Additionally, if MaxRenderWidth and MaxRenderHeight values do not equal respectively the max_frame_width_minus_1 + 1 and max_frame_height_minus_1 + 1 values of the Sequence Header OBU, a PixelAspectRatioBox box SHALL be present in the sample entry and set such that:
hSpacing / vSpacing = MaxRenderWidth * (max_frame_height_minus_1 + 1) /
                        ((max_frame_width_minus_1 + 1) * MaxRenderHeight)

The compressorname field of the VisualSampleEntry is an informative name. It is formatted in a fixed 32-byte field, with the first byte set to the number of bytes to be displayed, followed by that number of bytes of displayable data, followed by padding to complete 32 bytes total (including the size byte). The value "\012AOM Coding" is RECOMMENDED; the first byte is a count of the remaining bytes, here represented by \012, which (being octal 12) is decimal 10, the number of bytes in the rest of the string.

NOTE: Parsers may ignore the value of the compressorname field. It is specified in this document simply for legacy and backwards compatibility reasons.

The config field SHALL contain an AV1CodecConfigurationBox that applies to the samples associated with this sample entry.

NOTE: Multiple instances of AV1SampleEntry may be required when the track contains samples requiring a AV1CodecConfigurationBox with different characteristics.

Optional boxes not specifically mentioned here can be present, in particular those indicated in the definition of the VisualSampleEntry in [ISOBMFF].

2.3. AV1 Codec Configuration Box

2.3.1. Definition

Box Type:  av1C
Container: AV1 Sample Entry ('av01')
Mandatory: Yes 
Quantity:  Exactly One 

2.3.2. Description

The AV1CodecConfigurationBox contains decoder configuration information that SHALL be valid for every sample that references the sample entry.

2.3.3. Syntax

class AV1CodecConfigurationBox
extends Box('av1C')
  AV1CodecConfigurationRecord av1Config;

aligned(8) class AV1CodecConfigurationRecord
  unsigned int(1) marker = 1;
  unsigned int(7) version = 1;
  unsigned int(3) seq_profile;
  unsigned int(5) seq_level_idx_0;
  unsigned int(1) seq_tier_0;
  unsigned int(1) high_bitdepth;
  unsigned int(1) twelve_bit;
  unsigned int(1) monochrome;
  unsigned int(1) chroma_subsampling_x;
  unsigned int(1) chroma_subsampling_y;
  unsigned int(2) chroma_sample_position;
  unsigned int(3) reserved = 0;

  unsigned int(1) initial_presentation_delay_present;
  if(initial_presentation_delay_present) {
    unsigned int(4) initial_presentation_delay_minus_one;
  } else {
    unsigned int(4) reserved = 0;

  unsigned int(8) configOBUs[];

2.3.4. Semantics

The marker field SHALL be set to 1.

NOTE: The marker bit ensures that the bit pattern of the first byte of the AV1CodecConfigurationRecord cannot be mistaken for an OBU Header byte.

The version field indicates the version of the AV1CodecConfigurationRecord. The value SHALL be set to 1 for AV1CodecConfigurationRecord.

The seq_profile field indicates the AV1 profile and SHALL be equal to the seq_profile value from the Sequence Header OBU. The seq_level_idx_0 field SHALL be equal to the value of seq_level_idx[0] from the Sequence Header OBU. The seq_tier_0 field SHALL be equal to the value of seq_tier[0] from the Sequence Header OBU. The high_bitdepth field SHALL be equal to the value of high_bitdepth flag from the Sequence Header OBU. The twelve_bit field SHALL be equal to the value of the twelve_bit flag from the Sequence Header OBU. When twelve_bit is not present in the Sequence Header OBU the AV1CodecConfigurationRecord twelve_bit value SHALL be 0. The monochrome field SHALL be equal to the value of the mono_chrome flag from the Sequence Header OBU. The chroma_subsampling_x field SHALL be equal to the value of the subsampling_x value from the Sequence Header OBU. The chroma_subsampling_y field SHALL be equal to the value of the subsampling_y value from the Sequence Header OBU. The chroma_sample_position field SHALL be equal to the value of the chroma_sample_position value from the Sequence Header OBU. When not specified in the Sequence Header OBU, and not defined by the conditions specified in the [AV1] color_config, the values of chroma_subsampling_x, chroma_subsampling_y, and chroma_sample_position SHALL be 0.

The initial_presentation_delay_present field indicates the presence of the initial_presentation_delay_minus_one field.

The initial_presentation_delay_minus_one field indicates the number of samples (minus one) that need to be decoded prior to starting the presentation of the first sample associated with this sample entry in order to guarantee that each sample will be decoded prior to its presentation time under the constraints of the first level value indicated by seq_level_idx in the Sequence Header OBU (in the configOBUs field or in the associated samples). More precisely, the following procedure SHALL not return any error:

NOTE: With the above procedure, when smooth presentation can be guaranteed after decoding the first sample, initial_presentation_delay_minus_one is 0.

NOTE: Because the above procedure considers all OBUs in all samples associated with a sample entry, if these OBUS form multiple coded video sequences which would have different values of initial_presentation_delay_minus_one if considered separately, the sample entry would signal the larger value.

The difference between initial_presentation_delay_minus_one and initial_display_delay_minus_1 can be illustrated by considering the following example:
a b c d e f g h

where letters correspond to frames. Assume that initial_display_delay_minus_1 is 2, i.e. that once frame c has been decoded, all other frames in the bitstream can be presented on time. If those frames were grouped into temporal units and samples as follows:

[a] [b c d] [e] [f] [g] [h]

initial_presentation_delay_minus_one would be 1 because it takes presentation of 2 samples to ensure that c is decoded. But if the frames were grouped as follows:

[a] [b] [c] [d e f] [g] [h]

initial_presentation_delay_minus_one would be 2 because it takes presentation of 3 samples to ensure that c is decoded.

The configOBUs field contains zero or more OBUs. Any OBU may be present provided that the following procedures produce compliant AV1 bitstreams:

NOTE: If a Sequence Header OBU is stored in the configOBUs field, because a sync sample also stores the Sequence Header OBU, this procedure will produce 2 consecutive and identical Sequence Header OBUs. Compliant [AV1] decoders are expected to handle that.

Additionally, the configOBUs field SHALL contain at most one Sequence Header OBU and if present, it SHALL be the first OBU.

NOTE: The configOBUs field is expected to contain only one Sequence Header OBU and zero or more Metadata OBUs when applicable to all the associated samples.

OBUs stored in the configOBUs field follow the open_bitstream_unit Low Overhead Bitstream Format syntax as specified in [AV1]. The flag obu_has_size_field SHALL be set to 1, indicating that the size of the OBU payload follows the header, and that it is coded using LEB128.

When a Sequence Header OBU is contained within the configOBUs of the AV1CodecConfigurationRecord, the values present in the Sequence Header OBU contained within configOBUs SHALL match the values of the AV1CodecConfigurationRecord. When the samples associated with a sample entry do not contain any sync sample, a Sequence Header OBU SHALL be present in the configOBUs field of the AV1CodecConfigurationRecord of that sample entry.

The presentation times of AV1 samples are given by the ISOBMFF structures. The timing_info_present_flag in the Sequence Header OBU (in the configOBUs field or in the associated samples) SHOULD be set to 0. If set to 1, the timing_info structure of the Sequence Header OBU, the frame_presentation_time and buffer_removal_time fields of the Frame Header OBUs, if present, SHALL be ignored for the purpose of timed processing of the ISOBMFF file.

The sample entry SHOULD contain a colr box with a colour_type set to nclx. If a colr box with a colour_type set to nclx is present, the following applies: When configOBUs does not contain a Sequence Header OBU, a colr box with a colour_type set to nclx SHALL be present.

For sample entries corresponding to HDR content, the following applies:

NOTE: The MasteringDisplayColourVolumeBox mdcv and ContentLightLevelBox clli have identical syntax to the SMPTE2086MasteringDisplayMetadataBox SmDm and ContentLightLevelBox CoLL, except that they are of type Box and not FullBox. However, the semantics of the MasteringDisplayColourVolumeBox and SMPTE2086MasteringDisplayMetadataBox have important differences and SHOULD not be confused.

NOTE: In the MasteringDisplayColourVolumeBox mdcv, the representation and coding of some fields are different from the representation and coding of the corresponding fields in the Metadata OBU of type METADATA_TYPE_HDR_MDCV. Because of these differences, some values coded in the MasteringDisplayColourVolumeBox mdcv may not have the same precision in the Metadata OBU of type METADATA_TYPE_HDR_MDCV, and vice versa.

Additional boxes may be provided at the end of the VisualSampleEntry as permitted by ISOBMFF, that may represent redundant or similar information to the one provided in some OBUs contained in the AV1CodecConfigurationBox. If the box definition does not indicate that its information overrides the OBU information, in case of conflict, the OBU information SHOULD be considered authoritative.

2.4. AV1 Sample Format

For tracks using the AV1SampleEntry, an AV1 Sample has the following constraints:

NOTE: When extracting OBUs from an ISOBMFF file, and depending on the capabilities of the decoder processing these OBUs, ISOBMFF parsers MAY need to either: set the obu_has_size_field to 1 for some OBUs if not already set, add the size field in this case, and add Temporal Delimiter OBU; or use the length-delimited bitstream format as defined in Annex B of AV1. If encryption is used, similar operations MAY have to be done before or after decryption depending on the demuxer/decryptor/decoder architecture.

If an AV1 Sample is signaled as a sync sample (in the SyncSampleBox or by setting sample_is_non_sync_sample to 0), it SHALL be a Random Access Point as defined in [AV1], i.e. satisfy the following constraints:

NOTE: Within this definition, a sync sample may contain additional frames that are not Key Frames. The fact that none of them is the first frame in the temporal unit ensures that they are decodable.

NOTE: Other types of OBUs such as metadata OBUs could be present before the Sequence Header OBU.

Intra-only frames SHOULD be signaled using the sample_depends_on flag set to 2. Delayed Random Access Points SHOULD be signaled using sample groups and the AV1ForwardKeyFrameSampleGroupEntry. Switch Frames SHOULD be signaled using sample groups and the AV1SwitchFrameSampleGroupEntry.

Additionally, if a file contains multiple tracks that are alternative representations of the same content, in particular using Switch Frames, those tracks SHOULD be marked as belonging to the same alternate group and SHOULD use a track selection box with an appropriate attribute (e.g. bitr).

In tracks using the AV1SampleEntry, the ctts box and composition offsets in movie fragments SHALL NOT be used. Similarly, the is_leading flag, if used, SHALL be set to 0 or 2. When a temporal unit contains more than one frame, the sample corresponding to that temporal unit MAY be marked using the AV1MultiFrameSampleGroupEntry. Metadata OBUs may be carried in sample data. In this case, the AV1MetadataSampleGroupEntry SHOULD be used. If the metadata OBUs are static for the entire set of samples associated with a given sample description entry, they SHOULD also be in the OBU array in the sample description entry.

Unless explicitely stated, the grouping_type_parameter is not defined for the SampleToGroupBox with grouping types defined in this specification.

2.5. AV1 Forward Key Frame sample group entry

2.5.1. Definition

Group Type: av1f
Container:  Sample Group Description Box ('sgpd')
Mandatory:  No 
Quantity:   Zero or more .

2.5.2. Description

The AV1ForwardKeyFrameSampleGroupEntry documents samples that contain a Delayed Random Access Point that are followed at a given distance in the bitstream by a Key Frame Dependent Recovery Point.

2.5.3. Syntax

class AV1ForwardKeyFrameSampleGroupEntry
extends VisualSampleGroupEntry('av1f')
  unsigned int(8) fwd_distance;

2.5.4. Semantics

The fwd_distance field indicates the number of samples between this sample and the next sample containing the associated Key Frame Dependent Recovery Point. 0 means the next sample.

2.6. AV1 Multi-Frame sample group entry

2.6.1. Definition

Group Type: av1m
Container:  Sample Group Description Box ('sgpd')
Mandatory:  No 
Quantity:   Zero or more .

2.6.2. Description

The AV1MultiFrameSampleGroupEntry documents samples that contain multiple frames.

2.6.3. Syntax

class AV1MultiFrameSampleGroupEntry
extends VisualSampleGroupEntry('av1m')

2.7. AV1 Switch Frame sample group entry

2.7.1. Definition

Group Type: av1s
Container:  Sample Group Description Box ('sgpd')
Mandatory:  No 
Quantity:   Zero or more .

2.7.2. Description

The AV1SwitchFrameSampleGroupEntry documents samples that start with a Switch Frame.

2.7.3. Syntax

class AV1SwitchFrameSampleGroupEntry
extends VisualSampleGroupEntry('av1s')

2.8. AV1 Metadata sample group entry

2.8.1. Definition

Group Type: av1M
Container:  Sample Group Description Box ('sgpd')
Mandatory:  No 
Quantity:   Zero or more .

2.8.2. Description

The AV1MetadataSampleGroupEntry documents samples that contain metadata OBUs. The grouping_type_parameter can be used to identify samples containing metadata OBUs of a given type. If no grouping_type_parameter is provided, the sample group entry identifies samples containing metadata OBUs for which the metadata_type is unknown.

2.8.3. Syntax

class AV1MetadataSampleGroupEntry
extends VisualSampleGroupEntry('av1M')

For this sample group entry, the grouping_type_parameter syntax is as follows:

   unsigned int (8) metadata_type;
   unsigned int (24) metadata_specific_parameters;

2.8.4. Semantics

metadata_type is a 8-bit field whose value is the value of the metadata_type field defined in [AV1], when it is equal or lower than 255. metadata_type values above 255 are not supported by this sample group.

metadata_specific_parameters provides an additional part of the grouping_type_parameter, which MAY be used to distinguish different sample groups having the same metadata_type but different sub-parameters. In this version of the specification, metadata_specific_parameters is only defined when metadata_type is set to METADATA_TYPE_ITUT_T35 in which case its value SHALL be set to the first 24 bits of the metadata_itut_t35 structure. For other types of metadata, its value SHOULD be set to 0. In all cases, when the grouping_type_parameter is used, readers processing sample groups SHALL use the entire value of grouping_type_parameter.

NOTE: The current design is constrained to using only 3 bytes for ITU-T T.35 identification, which typically suffices for the itu_t_t35_country_code and the itu_t_t35_terminal_provider_code identification. Consequently, inspection of the payload becomes essential if an implementation aims to determine the values of subsequent bytes, for instance, the itu_t_t35_terminal_provider_oriented_code.

3. CMAF AV1 track format

[CMAF] defines structural constraints on ISOBMFF files additional to [ISOBMFF] for the purpose of, for example, adaptive streaming or for protected files. Conformance to these structural constraints is signaled by the presence of the brands cmfc or cmf2 in the FileTypeBox.

NOTE: It is important to note that while the cmf2 brand does not introduce any new requirements compared to the previously defined cmfc brand, it further restricts the cmfc constraints.

For compatibility reasons, when the cmf2 brand is used, the cmfc brand SHOULD also be included in the FileTypeBox.

If a CMAF Video Track uses the brand av01, it is called a CMAF AV1 Track and the following constraints, defining the CMAF Media Profile for AV1, apply:

When protected, CMAF AV1 Tracks SHALL use the signaling defined in [CMAF], which in turn relies on [CENC], with the provisions specified in § 4 Common Encryption.

4. Common Encryption

CMAF AV1 Tracks and non-segmented AV1 files MAY be protected. If protected, they SHALL conform to [CENC]. Files SHOULD be protected using the cbcs protection scheme and MAY be protected using the cenc protection scheme. When the protected scheme cenc is used, samples SHALL be protected using subsample encryption and SHALL NOT use pattern encryption. When the protected scheme cbcs is used, samples SHALL be protected using subsample encryption and SHALL use pattern encryption. [CENC] recommends that the Block Pattern length be 10, i.e. crypt_byte_block + skip_byte_block = 10, where a Block is of size 16-bytes. In this specification, the combination of crypt_byte_block and skip_byte_block SHALL be one of the following, with the first one being recommended:

4.1. General Subsample Encryption constraints

Within protected samples, the following constraints apply:

NOTE: Version 0 of the saiz box as defined in [ISOBMFF] can only describe Sample Auxiliary Information whose size does not exceed 255 bytes. In the case of AV1 streams that use a large number of tiles or a large number of frames per sample, when following the encryption requirements defined in this section the size of the corresponding Sample Auxiliary Information may exceed that limit. Until updates are made to [ISOBMFF], authors are encouraged to avoid reaching the limit.

4.2. Subsample Encryption Illustration

Figure #1 illustrates Subsample based encryption of AV1.
Subsample-based AV1 encryption
Subsample-based AV1 encryption.

5. Codecs Parameter String

DASH and other applications require defined values for the Codecs parameter specified in [RFC6381] for ISO Media tracks. The codecs parameter string for the AOM AV1 codec is as follows:

<sample entry 4CC>.<profile>.<level><tier>.<bitDepth>.<monochrome>.<chromaSubsampling>.

All fields following the sample entry 4CC are expressed as double digit decimals, unless indicated otherwise. Leading or trailing zeros cannot be omitted.

The profile parameter value, represented by a single digit decimal, SHALL equal the value of seq_profile in the Sequence Header OBU. The level parameter value SHALL equal the first level value indicated by seq_level_idx in the Sequence Header OBU. The tier parameter value SHALL be equal to M when the first seq_tier value in the Sequence Header OBU is equal to 0, and H when it is equal to 1. The bitDepth parameter value SHALL equal the value of BitDepth variable as defined in [AV1] derived from the Sequence Header OBU. The monochrome parameter value, represented by a single digit decimal, SHALL equal the value of mono_chrome in the Sequence Header OBU. The chromaSubsampling parameter value, represented by a three-digit decimal, SHALL have its first digit equal to subsampling_x and its second digit equal to subsampling_y. If both subsampling_x and subsampling_y are set to 1, then the third digit SHALL be equal to chroma_sample_position, otherwise it SHALL be set to 0.

The colorPrimaries, transferCharacteristics, matrixCoefficients, and videoFullRangeFlag parameter values are set as follows:

NOTE: It is encouraged that a colr box be present. The colr box simplifies the task of the codecs parameter generator.

NOTE: If the encoded video uses a color space that is not registered in [CICP] and the file doesn’t explicitly code 2/2/2 either in the colr box or in the Sequence Header OBU (with color_description_present_flag set to 1), the derived codecs parameter string will declare ITU-R BT.709 (1/1/1). To avoid this behavior, a colr box should be used.

The videoFullRangeFlag is represented by a single digit.

If the codecs parameter string ends with "." (containing all the default values below), that trailing part of the string SHOULD be omitted.

For example, codecs="av01.0.04M." represents AV1 Main Profile, level 3.0, Main tier, 10-bit content, non-monochrome, with 4:2:0 chroma subsampling co-located with (0, 0) luma sample, ITU-R BT.2100 color primaries, ITU-R BT.2100 PQ transfer characteristics, ITU-R BT.2100 YCbCr color matrix, and studio swing representation.

The parameters sample entry 4CC, profile, level, tier, and bitDepth are all mandatory fields. If any of these fields are empty, or not within their allowed range, the processing device SHOULD treat it as an error. All the other fields (including their leading '.') are optional, mutually inclusive (all or none) fields. If not specified then the values listed in the table below are assumed.
mono_chrome 0
chromaSubsampling 110 (4:2:0)
colorPrimaries 01 (ITU-R BT.709)
transferCharacteristics 01 (ITU-R BT.709)
matrixCoefficients 01 (ITU-R BT.709)
videoFullRangeFlag 0 (studio swing representation)

The string codecs="av01.0.01M.08" in this case would represent AV1 Main Profile, level 2.1, Main tier, 8-bit content with 4:2:0 chroma subsampling, ITU-R BT.709 color primaries, transfer characteristics, matrix coefficients, and studio swing representation.

If any character that is not '.', digits, part of the AV1 4CC, or a tier value is encountered, the string SHALL be interpreted ignoring all the characters starting from that character.

6. Changes since v1.2.0 release


Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.


Terms defined by this specification

Terms defined by reference


Normative References

AV1 Bitstream & Decoding Process Specification. Standard. URL: https://aomediacodec.github.io/av1-spec/av1-spec.pdf
Information technology — MPEG systems technologies — Part 7: Common encryption in ISO base media file format files. Standard. URL: https://www.iso.org/standard/68042.html
Information technology — Multimedia application format (MPEG-A) — Part 19: Common media application format (CMAF) for segmented media. Standard. URL: https://www.iso.org/standard/71975.html
Information technology — Coding of audio-visual objects — Part 12: ISO base media file format. Standard. URL: https://www.iso.org/standard/83102.html
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://datatracker.ietf.org/doc/html/rfc2119
R. Gellens; D. Singer; P. Frojdh. The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types. August 2011. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc6381

Informative References

Coding-independent code points for video signal type identification. Standard. URL: https://www.itu.int/rec/T-REC-H.273/en