rfc9559-iana-sg.txt   rfc9559.txt 
skipping to change at line 977 skipping to change at line 977
chapter codec data. The format depends on the ChapProcessCodecID chapter codec data. The format depends on the ChapProcessCodecID
used; see Section 5.1.7.1.4.15. used; see Section 5.1.7.1.4.15.
5.1.2.8.2. ChapterTranslateCodec Element 5.1.2.8.2. ChapterTranslateCodec Element
id / type: 0x69BF / uinteger id / type: 0x69BF / uinteger
path: \Segment\Info\ChapterTranslate\ChapterTranslateCodec path: \Segment\Info\ChapterTranslate\ChapterTranslateCodec
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: Applies to the chapter codec of the given chapter definition: Applies to the chapter codec of the given chapter
edition(s); see Section 5.1.7.1.4.15. edition(s); see Section 5.1.7.1.4.15.
defined values: See Table 1. Further values can be added in the defined values: See Table 1. Additional values can be registered in
IANA registry found in Section 27.2. the "Matroska Chapter Codec IDs" registry defined in Section 27.2.
+=======+=================+============================+ +=======+=================+============================+
| value | label | definition | | value | label | definition |
+=======+=================+============================+ +=======+=================+============================+
| 0 | Matroska Script | Chapter commands using the | | 0 | Matroska Script | Chapter commands using the |
| | | Matroska Script codec. | | | | Matroska Script codec. |
+-------+-----------------+----------------------------+ +-------+-----------------+----------------------------+
| 1 | DVD-menu | Chapter commands using the | | 1 | DVD-menu | Chapter commands using the |
| | | DVD-like codec. | | | | DVD-like codec. |
+-------+-----------------+----------------------------+ +-------+-----------------+----------------------------+
skipping to change at line 1283 skipping to change at line 1283
definition: A UID that identifies the Track. definition: A UID that identifies the Track.
stream copy: True (Section 8) stream copy: True (Section 8)
5.1.4.1.3. TrackType Element 5.1.4.1.3. TrackType Element
id / type: 0x83 / uinteger id / type: 0x83 / uinteger
path: \Segment\Tracks\TrackEntry\TrackType path: \Segment\Tracks\TrackEntry\TrackType
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: The TrackType defines the type of each frame found in definition: The TrackType defines the type of each frame found in
the Track. The value SHOULD be stored on 1 octet. the Track. The value SHOULD be stored on 1 octet.
defined values: See Table 3. Further values can be added in the defined values: See Table 3. Additional values can be registered in
IANA registry found in Section 27.3. the "Track Types" registry defined in Section 27.3.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+==========+==========================================+ +=======+==========+==========================================+
| value | label | contents of each frame | | value | label | contents of each frame |
+=======+==========+==========================================+ +=======+==========+==========================================+
| 1 | video | An image. | | 1 | video | An image. |
+-------+----------+------------------------------------------+ +-------+----------+------------------------------------------+
| 2 | audio | Audio samples. | | 2 | audio | Audio samples. |
+-------+----------+------------------------------------------+ +-------+----------+------------------------------------------+
| 3 | complex | A mix of different other TrackType. The | | 3 | complex | A mix of different other TrackType. The |
skipping to change at line 1631 skipping to change at line 1631
the chapter codec data. The format depends on the the chapter codec data. The format depends on the
ChapProcessCodecID used; see Section 5.1.7.1.4.15. ChapProcessCodecID used; see Section 5.1.7.1.4.15.
5.1.4.1.27.2. TrackTranslateCodec Element 5.1.4.1.27.2. TrackTranslateCodec Element
id / type: 0x66BF / uinteger id / type: 0x66BF / uinteger
path: \Segment\Tracks\TrackEntry\TrackTranslate\TrackTranslateCodec path: \Segment\Tracks\TrackEntry\TrackTranslate\TrackTranslateCodec
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: Applies to the chapter codec of the given chapter definition: Applies to the chapter codec of the given chapter
edition(s); see Section 5.1.7.1.4.15. edition(s); see Section 5.1.7.1.4.15.
defined values: See Table 4. Further values can be added in the defined values: See Table 4. Additional values can be registered in
IANA registry found in Section 27.2. the "Matroska Chapter Codec IDs" registry defined in Section 27.2.
+=======+=================+============================+ +=======+=================+============================+
| value | label | definition | | value | label | definition |
+=======+=================+============================+ +=======+=================+============================+
| 0 | Matroska Script | Chapter commands using the | | 0 | Matroska Script | Chapter commands using the |
| | | Matroska Script codec. | | | | Matroska Script codec. |
+-------+-----------------+----------------------------+ +-------+-----------------+----------------------------+
| 1 | DVD-menu | Chapter commands using the | | 1 | DVD-menu | Chapter commands using the |
| | | DVD-like codec. | | | | DVD-like codec. |
+-------+-----------------+----------------------------+ +-------+-----------------+----------------------------+
skipping to change at line 1736 skipping to change at line 1736
Table 6: FieldOrder Values Table 6: FieldOrder Values
5.1.4.1.28.3. StereoMode Element 5.1.4.1.28.3. StereoMode Element
id / type / default: 0x53B8 / uinteger / 0 id / type / default: 0x53B8 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\StereoMode path: \Segment\Tracks\TrackEntry\Video\StereoMode
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
minver: 3 minver: 3
definition: Stereo-3D video mode. See Section 18.10 for more definition: Stereo-3D video mode. See Section 18.10 for more
details. details.
defined values: See Table 7. Further values can be added in the defined values: See Table 7. Additional values can be registered in
IANA registry found in Section 27.11. the "Stereo Modes" registry defined in Section 27.11.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+===================================================+ +=======+===================================================+
| value | label | | value | label |
+=======+===================================================+ +=======+===================================================+
| 0 | mono | | 0 | mono |
+-------+---------------------------------------------------+ +-------+---------------------------------------------------+
| 1 | side by side (left eye first) | | 1 | side by side (left eye first) |
+-------+---------------------------------------------------+ +-------+---------------------------------------------------+
| 2 | top - bottom (right eye is first) | | 2 | top - bottom (right eye is first) |
skipping to change at line 1787 skipping to change at line 1787
id / type / default: 0x53C0 / uinteger / 0 id / type / default: 0x53C0 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\AlphaMode path: \Segment\Tracks\TrackEntry\Video\AlphaMode
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
minver: 3 minver: 3
definition: Indicates whether the BlockAdditional element with definition: Indicates whether the BlockAdditional element with
BlockAddID of "1" contains Alpha data as defined by the Codec BlockAddID of "1" contains Alpha data as defined by the Codec
Mapping for the CodecID. Undefined values (i.e., values other Mapping for the CodecID. Undefined values (i.e., values other
than 0 or 1) SHOULD NOT be used, as the behavior of known than 0 or 1) SHOULD NOT be used, as the behavior of known
implementations is different. implementations is different.
defined values: See Table 8. Further values can be added in the defined values: See Table 8. Additional values can be registered in
IANA registry found in Section 27.5. the "Alpha Modes" registry defined in Section 27.5.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+=========+============================================+ +=======+=========+============================================+
| value | label | definition | | value | label | definition |
+=======+=========+============================================+ +=======+=========+============================================+
| 0 | none | The BlockAdditional element with | | 0 | none | The BlockAdditional element with |
| | | BlockAddID of "1" does not exist or SHOULD | | | | BlockAddID of "1" does not exist or SHOULD |
| | | NOT be considered as containing such data. | | | | NOT be considered as containing such data. |
+-------+---------+--------------------------------------------+ +-------+---------+--------------------------------------------+
| 1 | present | The BlockAdditional element with | | 1 | present | The BlockAdditional element with |
skipping to change at line 1936 skipping to change at line 1936
+-----------+---------------------------------------------------+ +-----------+---------------------------------------------------+
Table 11: DisplayHeight Implementation Notes Table 11: DisplayHeight Implementation Notes
5.1.4.1.28.14. DisplayUnit Element 5.1.4.1.28.14. DisplayUnit Element
id / type / default: 0x54B2 / uinteger / 0 id / type / default: 0x54B2 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\DisplayUnit path: \Segment\Tracks\TrackEntry\Video\DisplayUnit
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: How DisplayWidth and DisplayHeight are interpreted. definition: How DisplayWidth and DisplayHeight are interpreted.
defined values: See Table 12. Further values can be added in the defined values: See Table 12. Additional values can be registered
IANA registry found in Section 27.12. in the "Display Units" registry defined in Section 27.12.
+=======+======================+ +=======+======================+
| value | label | | value | label |
+=======+======================+ +=======+======================+
| 0 | pixels | | 0 | pixels |
+-------+----------------------+ +-------+----------------------+
| 1 | centimeters | | 1 | centimeters |
+-------+----------------------+ +-------+----------------------+
| 2 | inches | | 2 | inches |
+-------+----------------------+ +-------+----------------------+
skipping to change at line 2105 skipping to change at line 2105
ChromaSubsamplingVert. ChromaSubsamplingVert.
stream copy: True (Section 8) stream copy: True (Section 8)
5.1.4.1.28.23. ChromaSitingHorz Element 5.1.4.1.28.23. ChromaSitingHorz Element
id / type / default: 0x55B7 / uinteger / 0 id / type / default: 0x55B7 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\Colour\ChromaSitingHorz path: \Segment\Tracks\TrackEntry\Video\Colour\ChromaSitingHorz
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
minver: 4 minver: 4
definition: How chroma is subsampled horizontally. definition: How chroma is subsampled horizontally.
defined values: See Table 15. Further values can be added in the defined values: See Table 15. Additional values can be registered
IANA registry found in Section 27.15. in the "Horizontal Chroma Sitings" registry defined in
Section 27.15.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+=================+ +=======+=================+
| value | label | | value | label |
+=======+=================+ +=======+=================+
| 0 | unspecified | | 0 | unspecified |
+-------+-----------------+ +-------+-----------------+
| 1 | left collocated | | 1 | left collocated |
+-------+-----------------+ +-------+-----------------+
| 2 | half | | 2 | half |
skipping to change at line 2129 skipping to change at line 2130
Table 15: Table 15:
ChromaSitingHorz Values ChromaSitingHorz Values
5.1.4.1.28.24. ChromaSitingVert Element 5.1.4.1.28.24. ChromaSitingVert Element
id / type / default: 0x55B8 / uinteger / 0 id / type / default: 0x55B8 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\Colour\ChromaSitingVert path: \Segment\Tracks\TrackEntry\Video\Colour\ChromaSitingVert
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
minver: 4 minver: 4
definition: How chroma is subsampled vertically. definition: How chroma is subsampled vertically.
defined values: See Table 16. Further values can be added in the defined values: See Table 16. Additional values can be registered
IANA registry found in Section 27.16. in the "Vertical Chroma Sitings" registry defined in
Section 27.16.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+================+ +=======+================+
| value | label | | value | label |
+=======+================+ +=======+================+
| 0 | unspecified | | 0 | unspecified |
+-------+----------------+ +-------+----------------+
| 1 | top collocated | | 1 | top collocated |
+-------+----------------+ +-------+----------------+
| 2 | half | | 2 | half |
skipping to change at line 2154 skipping to change at line 2156
ChromaSitingVert ChromaSitingVert
Values Values
5.1.4.1.28.25. Range Element 5.1.4.1.28.25. Range Element
id / type / default: 0x55B9 / uinteger / 0 id / type / default: 0x55B9 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\Colour\Range path: \Segment\Tracks\TrackEntry\Video\Colour\Range
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
minver: 4 minver: 4
definition: Clipping of the color ranges. definition: Clipping of the color ranges.
defined values: See Table 17. Further values can be added in the defined values: See Table 17. Additional values can be defined in
IANA registry found in Section 27.17. the "Color Ranges" registry defined in Section 27.17.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+=========================================================+ +=======+=========================================================+
| value | label | | value | label |
+=======+=========================================================+ +=======+=========================================================+
| 0 | unspecified | | 0 | unspecified |
+-------+---------------------------------------------------------+ +-------+---------------------------------------------------------+
| 1 | broadcast range | | 1 | broadcast range |
+-------+---------------------------------------------------------+ +-------+---------------------------------------------------------+
| 2 | full range (no clipping) | | 2 | full range (no clipping) |
skipping to change at line 2440 skipping to change at line 2442
vertically. vertically.
stream copy: True (Section 8) stream copy: True (Section 8)
5.1.4.1.28.42. ProjectionType Element 5.1.4.1.28.42. ProjectionType Element
id / type / default: 0x7671 / uinteger / 0 id / type / default: 0x7671 / uinteger / 0
path: \Segment\Tracks\TrackEntry\Video\Projection\ProjectionType path: \Segment\Tracks\TrackEntry\Video\Projection\ProjectionType
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
minver: 4 minver: 4
definition: Describes the projection used for this video track. definition: Describes the projection used for this video track.
defined values: See Table 20. Further values can be added in the defined values: See Table 20. Additional values can be registered
IANA registry found in Section 27.13. in the "Projection Types" registry defined in Section 27.13.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+=================+ +=======+=================+
| value | label | | value | label |
+=======+=================+ +=======+=================+
| 0 | rectangular | | 0 | rectangular |
+-------+-----------------+ +-------+-----------------+
| 1 | equirectangular | | 1 | equirectangular |
+-------+-----------------+ +-------+-----------------+
| 2 | cubemap | | 2 | cubemap |
skipping to change at line 2643 skipping to change at line 2645
stream copy: True (Section 8) stream copy: True (Section 8)
5.1.4.1.30.4. TrackPlaneType Element 5.1.4.1.30.4. TrackPlaneType Element
id / type: 0xE6 / uinteger id / type: 0xE6 / uinteger
path: \Segment\Tracks\TrackEntry\TrackOperation\TrackCombinePlanes\T path: \Segment\Tracks\TrackEntry\TrackOperation\TrackCombinePlanes\T
rackPlane\TrackPlaneType rackPlane\TrackPlaneType
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
minver: 3 minver: 3
definition: The kind of plane this track corresponds to. definition: The kind of plane this track corresponds to.
defined values: See Table 22. Further values can be added in the defined values: See Table 22. Additional values can be registered
IANA registry found in Section 27.14. in the "Track Plane Types" registry defined in Section 27.14.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+============+ +=======+============+
| value | label | | value | label |
+=======+============+ +=======+============+
| 0 | left eye | | 0 | left eye |
+-------+------------+ +-------+------------+
| 1 | right eye | | 1 | right eye |
+-------+------------+ +-------+------------+
| 2 | background | | 2 | background |
skipping to change at line 2722 skipping to change at line 2724
stream copy: True (Section 8) stream copy: True (Section 8)
5.1.4.1.31.3. ContentEncodingScope Element 5.1.4.1.31.3. ContentEncodingScope Element
id / type / default: 0x5032 / uinteger / 1 id / type / default: 0x5032 / uinteger / 1
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncodingScope ntentEncodingScope
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: A bit field that describes which elements have been definition: A bit field that describes which elements have been
modified in this way. Values (big-endian) can be OR'ed. modified in this way. Values (big-endian) can be OR'ed.
defined values: See Table 23. Further values can be added in the defined values: See Table 23. Additional values can be registered
IANA registry found in Section 27.6. in the "Content Encoding Scopes" registry defined in Section 27.6.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+=========+============================================+ +=======+=========+============================================+
| value | label | definition | | value | label | definition |
+=======+=========+============================================+ +=======+=========+============================================+
| 1 | Block | All frame contents, excluding lacing data. | | 1 | Block | All frame contents, excluding lacing data. |
+-------+---------+--------------------------------------------+ +-------+---------+--------------------------------------------+
| 2 | Private | The track's CodecPrivate data. | | 2 | Private | The track's CodecPrivate data. |
+-------+---------+--------------------------------------------+ +-------+---------+--------------------------------------------+
| 4 | Next | The next ContentEncoding (next | | 4 | Next | The next ContentEncoding (next |
skipping to change at line 2750 skipping to change at line 2752
Table 23: ContentEncodingScope Values Table 23: ContentEncodingScope Values
5.1.4.1.31.4. ContentEncodingType Element 5.1.4.1.31.4. ContentEncodingType Element
id / type / default: 0x5033 / uinteger / 0 id / type / default: 0x5033 / uinteger / 0
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncodingType ntentEncodingType
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: A value describing the kind of transformation that is definition: A value describing the kind of transformation that is
applied. applied.
defined values: See Table 24. Further values can be added in the defined values: See Table 24. Additional values can be registered
IANA registry found in Section 27.7. in the "Content Encoding Types" registry defined in Section 27.7.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+=============+ +=======+=============+
| value | label | | value | label |
+=======+=============+ +=======+=============+
| 0 | Compression | | 0 | Compression |
+-------+-------------+ +-------+-------------+
| 1 | Encryption | | 1 | Encryption |
+-------+-------------+ +-------+-------------+
skipping to change at line 2785 skipping to change at line 2787
previous block is available in order to not prevent seeking. previous block is available in order to not prevent seeking.
stream copy: True (Section 8) stream copy: True (Section 8)
5.1.4.1.31.6. ContentCompAlgo Element 5.1.4.1.31.6. ContentCompAlgo Element
id / type / default: 0x4254 / uinteger / 0 id / type / default: 0x4254 / uinteger / 0
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentCompression\ContentCompAlgo ntentCompression\ContentCompAlgo
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: The compression algorithm used. definition: The compression algorithm used.
defined values: See Table 25. Further values can be added in the defined values: See Table 25. Additional values can be registered
IANA registry found in Section 27.8. in the "Compression Algorithms" registry defined in Section 27.8.
usage notes: Compression method "1" (bzlib) and "2" (lzo1x) lack usage notes: Compression method "1" (bzlib) and "2" (lzo1x) lack
proper documentation on the format, which limits implementation proper documentation on the format, which limits implementation
possibilities. Due to licensing conflicts on commonly available possibilities. Due to licensing conflicts on commonly available
libraries' compression methods, "2" (lzo1x) does not offer libraries' compression methods, "2" (lzo1x) does not offer
widespread interoperability. A Matroska Writer SHOULD NOT use widespread interoperability. A Matroska Writer SHOULD NOT use
these compression methods by default. A Matroska Reader MAY these compression methods by default. A Matroska Reader MAY
support methods "1" and "2" and SHOULD support other methods. support methods "1" and "2" and SHOULD support other methods.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+===========+========================================+ +=======+===========+========================================+
skipping to change at line 2844 skipping to change at line 2846
support encryption. support encryption.
stream copy: True (Section 8) stream copy: True (Section 8)
5.1.4.1.31.9. ContentEncAlgo Element 5.1.4.1.31.9. ContentEncAlgo Element
id / type / default: 0x47E1 / uinteger / 0 id / type / default: 0x47E1 / uinteger / 0
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentEncAlgo ntentEncryption\ContentEncAlgo
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: The encryption algorithm used. definition: The encryption algorithm used.
defined values: See Table 26. Further values can be added in the defined values: See Table 26. Additional values can be registered
IANA registry found in Section 27.9. in the "Encryption Algorithms" registry defined in Section 27.9.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+===========+============================================+ +=======+===========+============================================+
| value | label | definition | | value | label | definition |
+=======+===========+============================================+ +=======+===========+============================================+
| 0 | Not | The data are not encrypted. | | 0 | Not | The data are not encrypted. |
| | encrypted | | | | encrypted | |
+-------+-----------+--------------------------------------------+ +-------+-----------+--------------------------------------------+
| 1 | DES | Data Encryption Standard (DES) [FIPS46-3]. | | 1 | DES | Data Encryption Standard (DES) [FIPS46-3]. |
| | | This value SHOULD be avoided. | | | | This value SHOULD be avoided. |
skipping to change at line 2909 skipping to change at line 2911
Table 27: ContentEncAESSettings Implementation Notes Table 27: ContentEncAESSettings Implementation Notes
5.1.4.1.31.12. AESSettingsCipherMode Element 5.1.4.1.31.12. AESSettingsCipherMode Element
id / type: 0x47E8 / uinteger id / type: 0x47E8 / uinteger
path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co path: \Segment\Tracks\TrackEntry\ContentEncodings\ContentEncoding\Co
ntentEncryption\ContentEncAESSettings\AESSettingsCipherMode ntentEncryption\ContentEncAESSettings\AESSettingsCipherMode
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
minver: 4 minver: 4
definition: The AES cipher mode used in the encryption. definition: The AES cipher mode used in the encryption.
defined values: See Table 28. Further values can be added in the defined values: See Table 28. Additional values can be registered
IANA registry found in Section 27.10. in the "AES Cipher Modes" registry defined in Section 27.10.
notes: See Table 29. notes: See Table 29.
stream copy: True (Section 8) stream copy: True (Section 8)
+=======+=========+===================================+ +=======+=========+===================================+
| value | label | definition | | value | label | definition |
+=======+=========+===================================+ +=======+=========+===================================+
| 1 | AES-CTR | Counter [SP800-38A] | | 1 | AES-CTR | Counter [SP800-38A] |
+-------+---------+-----------------------------------+ +-------+---------+-----------------------------------+
| 2 | AES-CBC | Cipher Block Chaining [SP800-38A] | | 2 | AES-CBC | Cipher Block Chaining [SP800-38A] |
+-------+---------+-----------------------------------+ +-------+---------+-----------------------------------+
skipping to change at line 3322 skipping to change at line 3324
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess
definition: Contains all the commands associated with the Atom. definition: Contains all the commands associated with the Atom.
5.1.7.1.4.15. ChapProcessCodecID Element 5.1.7.1.4.15. ChapProcessCodecID Element
id / type / default: 0x6955 / uinteger / 0 id / type / default: 0x6955 / uinteger / 0
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess\ChapPr path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapProcess\ChapPr
ocessCodecID ocessCodecID
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: Contains the type of the codec used for processing. definition: Contains the type of the codec used for processing.
defined values: See Table 33. Further values can be added in the defined values: See Table 33. Additional values can be registered
IANA registry found in Section 27.2. in the "Matroska Chapter Codec IDs" registry defined in
Section 27.2.
+=======+=================+============================+ +=======+=================+============================+
| value | label | definition | | value | label | definition |
+=======+=================+============================+ +=======+=================+============================+
| 0 | Matroska Script | Chapter commands using the | | 0 | Matroska Script | Chapter commands using the |
| | | Matroska Script codec. | | | | Matroska Script codec. |
+-------+-----------------+----------------------------+ +-------+-----------------+----------------------------+
| 1 | DVD-menu | Chapter commands using the | | 1 | DVD-menu | Chapter commands using the |
| | | DVD-like codec. | | | | DVD-like codec. |
+-------+-----------------+----------------------------+ +-------+-----------------+----------------------------+
skipping to change at line 3416 skipping to change at line 3419
definition: Specifies which other elements the metadata represented definition: Specifies which other elements the metadata represented
by the tag value applies to. If empty or omitted, then the tag by the tag value applies to. If empty or omitted, then the tag
value describes everything in the Segment. value describes everything in the Segment.
5.1.8.1.1.1. TargetTypeValue Element 5.1.8.1.1.1. TargetTypeValue Element
id / type / default: 0x68CA / uinteger / 50 id / type / default: 0x68CA / uinteger / 50
path: \Segment\Tags\Tag\Targets\TargetTypeValue path: \Segment\Tags\Tag\Targets\TargetTypeValue
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: A number to indicate the logical level of the target. definition: A number to indicate the logical level of the target.
defined values: See Table 35. Further values can be added in the defined values: See Table 35. Additional values can be registered
IANA registry found in Section 27.4. in the "Tags Target Types" registry defined in Section 27.4.
+=======+==========================+================================+ +=======+==========================+================================+
| value | label | definition | | value | label | definition |
+=======+==========================+================================+ +=======+==========================+================================+
| 70 | COLLECTION | The highest hierarchical level | | 70 | COLLECTION | The highest hierarchical level |
| | | that tags can describe. | | | | that tags can describe. |
+-------+--------------------------+--------------------------------+ +-------+--------------------------+--------------------------------+
| 60 | EDITION / ISSUE / | A list of lower levels grouped | | 60 | EDITION / ISSUE / | A list of lower levels grouped |
| | VOLUME / OPUS / | together. | | | VOLUME / OPUS / | together. |
| | SEASON / SEQUEL | | | | SEASON / SEQUEL | |
skipping to change at line 4282 skipping to change at line 4285
<Timestamp>123456</Timestamp> <Timestamp>123456</Timestamp>
<SimpleBlock/> (octet 3 bit 0 set) <SimpleBlock/> (octet 3 bit 0 set)
... ...
</Cluster> </Cluster>
Figure 18: SimpleBlock with a Frame That References No Other Figure 18: SimpleBlock with a Frame That References No Other
Frame, with the EBML Tree Shown as XML Frame, with the EBML Tree Shown as XML
There may be cases where the use of BlockGroup is necessary, as the There may be cases where the use of BlockGroup is necessary, as the
frame may need a BlockDuration, BlockAdditions, CodecState, or frame may need a BlockDuration, BlockAdditions, CodecState, or
DiscardPadding element. For thoses cases, a SimpleBlock MUST NOT be DiscardPadding element. For those cases, a SimpleBlock MUST NOT be
used; the reference information SHOULD be recovered for non-RAP used; the reference information SHOULD be recovered for non-RAP
frames. frames.
<Cluster> <Cluster>
<Timestamp>123456</Timestamp> <Timestamp>123456</Timestamp>
<SimpleBlock/> (octet 3 bit 0 not set) <SimpleBlock/> (octet 3 bit 0 not set)
... ...
</Cluster> </Cluster>
Figure 19: SimpleBlock with a Frame That References Another Figure 19: SimpleBlock with a Frame That References Another
skipping to change at line 6126 skipping to change at line 6129
used for such high-level elements. Elements that are not expected to used for such high-level elements. Elements that are not expected to
be used often should use three-octet Element IDs. be used often should use three-octet Element IDs.
Elements found in Appendix A have an assigned Matroska Element ID for Elements found in Appendix A have an assigned Matroska Element ID for
historical reasons. These elements are not in use and SHOULD NOT be historical reasons. These elements are not in use and SHOULD NOT be
reused unless there are no other IDs available with the desired size. reused unless there are no other IDs available with the desired size.
Such IDs are marked as "Reclaimed" in the "Matroska Element IDs" Such IDs are marked as "Reclaimed" in the "Matroska Element IDs"
registry, as they could be used for other things in the future. registry, as they could be used for other things in the future.
Table 55 shows the initial contents of the "Matroska Element IDs" Table 55 shows the initial contents of the "Matroska Element IDs"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 55 is "IETF".
+============+=============================+======================+ +============+=============================+======================+
| Element ID | Element Name | Reference | | Element ID | Element Name | Reference |
+============+=============================+======================+ +============+=============================+======================+
| 0x80 | ChapterDisplay | RFC 9559, | | 0x80 | ChapterDisplay | RFC 9559, |
| | | Section 5.1.7.1.4.9 | | | | Section 5.1.7.1.4.9 |
+------------+-----------------------------+----------------------+ +------------+-----------------------------+----------------------+
| 0x83 | TrackType | RFC 9559, | | 0x83 | TrackType | RFC 9559, |
| | | Section 5.1.4.1.3 | | | | Section 5.1.4.1.3 |
+------------+-----------------------------+----------------------+ +------------+-----------------------------+----------------------+
skipping to change at line 6897 skipping to change at line 6899
+------------+-----------------------------+----------------------+ +------------+-----------------------------+----------------------+
| 0x1FFFFFFF | Reserved | RFC 9559 | | 0x1FFFFFFF | Reserved | RFC 9559 |
+------------+-----------------------------+----------------------+ +------------+-----------------------------+----------------------+
Table 55: Initial Contents of "Matroska Element IDs" Registry Table 55: Initial Contents of "Matroska Element IDs" Registry
27.2. Chapter Codec IDs Registry 27.2. Chapter Codec IDs Registry
IANA has created a new registry called the "Matroska Chapter Codec IANA has created a new registry called the "Matroska Chapter Codec
IDs" registry. The values correspond to the unsigned integer IDs" registry. The values correspond to the unsigned integer
ChapProcessCodecID, ChapterTranslateCodec and TrackTranslateCodec ChapProcessCodecID, ChapterTranslateCodec, and TrackTranslateCodec
values described in Section 5.1.7.1.4.15, Section 5.1.2.8.2 and values described in Section 5.1.7.1.4.15, Section 5.1.2.8.2, and
Section 5.1.4.1.27.2 respectively. Section 5.1.4.1.27.2, respectively.
To register a new Chapter Codec ID in this registry, one needs a To register a new Chapter Codec ID in this registry, one needs a
Chapter Codec ID, description, a Change Controller (IETF or email of Chapter Codec ID, a description, a Change Controller (IETF or email
registrant), and an optional Reference to a document describing the of registrant), and an optional Reference to a document describing
Chapter Codec ID. the Chapter Codec ID.
The Chapter Codec IDs are to be allocated according to the The Chapter Codec IDs are to be allocated according to the
"Specification Required" policy [RFC8126]. "Specification Required" policy [RFC8126].
Table 56 shows the initial contents of the "Chapter Codec IDs" Table 56 shows the initial contents of the "Chapter Codec IDs"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 56 is "IETF".
+==================+=================+===================+ +==================+=================+===================+
| Chapter Codec ID | Description | Reference | | Chapter Codec ID | Description | Reference |
+==================+=================+===================+ +==================+=================+===================+
| 0 | Matroska Script | RFC 9559, Section | | 0 | Matroska Script | RFC 9559, Section |
| | | 5.1.7.1.4.15 | | | | 5.1.7.1.4.15 |
+------------------+-----------------+-------------------+ +------------------+-----------------+-------------------+
| 1 | DVD-Menu | RFC 9559, Section | | 1 | DVD-Menu | RFC 9559, Section |
| | | 5.1.7.1.4.15 | | | | 5.1.7.1.4.15 |
+------------------+-----------------+-------------------+ +------------------+-----------------+-------------------+
Table 56: Initial Contents of "Chapter Codec IDs" Registry Table 56: Initial Contents of "Chapter Codec IDs" Registry
27.3. Track Types Registry 27.3. Track Types Registry
IANA has created a new registry called the "Track Types" registry. IANA has created a new registry called the "Track Types" registry.
The values correspond to the unsigned integer TrackType value The values correspond to the unsigned integer TrackType value
described in Section 5.1.4.1.3. described in Section 5.1.4.1.3.
To register a new Track Type in this registry, one needs an Track To register a new Track Type in this registry, one needs a Track Type
Type value, description, a Change Controller (IETF or email of value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the registrant), and an optional Reference to a document describing the
Track Type. Track Type.
The Track Types are to be allocated according to the "Specification The Track Types are to be allocated according to the "Specification
Required" policy [RFC8126]. Required" policy [RFC8126].
Table 57 shows the initial contents of the "Track Types" registry. Table 57 shows the initial contents of the "Track Types" registry.
Note that the Change Controller for all entries in Table 57 is The Change Controller for the initial entries is the IETF.
"IETF".
+============+=============+=============================+ +============+=============+=============================+
| Track Type | Description | Reference | | Track Type | Description | Reference |
+============+=============+=============================+ +============+=============+=============================+
| 1 | video | RFC 9559, Section 5.1.4.1.3 | | 1 | video | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+ +------------+-------------+-----------------------------+
| 2 | audio | RFC 9559, Section 5.1.4.1.3 | | 2 | audio | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+ +------------+-------------+-----------------------------+
| 3 | complex | RFC 9559, Section 5.1.4.1.3 | | 3 | complex | RFC 9559, Section 5.1.4.1.3 |
+------------+-------------+-----------------------------+ +------------+-------------+-----------------------------+
skipping to change at line 6972 skipping to change at line 6972
Table 57: Initial Contents of "Track Types" Registry Table 57: Initial Contents of "Track Types" Registry
27.4. Tags Target Types Registry 27.4. Tags Target Types Registry
IANA has created a new registry called the "Tags Target Types" IANA has created a new registry called the "Tags Target Types"
registry. The values correspond to the unsigned integer registry. The values correspond to the unsigned integer
TargetTypeValue value described in Section 5.1.8.1.1.1. TargetTypeValue value described in Section 5.1.8.1.1.1.
To register a new Tags Target Type in this registry, one needs a Tags To register a new Tags Target Type in this registry, one needs a Tags
Target Type value, description, a Change Controller (IETF or email of Target Type value, a description, a Change Controller (IETF or email
registrant), and an optional Reference to a document describing the of registrant), and an optional Reference to a document describing
Tags Target Type. the Tags Target Type.
The Tags Track Types are to be allocated according to the The Tags Track Types are to be allocated according to the
"Specification Required" policy [RFC8126]. "Specification Required" policy [RFC8126].
Table 58 shows the initial contents of the "Tags Target Types" Table 58 shows the initial contents of the "Tags Target Types"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 58 is "IETF".
+==================+==========================+===================+ +==================+==========================+===================+
| Tags Target Type | Description | Reference | | Tags Target Type | Description | Reference |
+==================+==========================+===================+ +==================+==========================+===================+
| 70 | COLLECTION | RFC 9559, Section | | 70 | COLLECTION | RFC 9559, Section |
| | | 5.1.8.1.1.1 | | | | 5.1.8.1.1.1 |
+------------------+--------------------------+-------------------+ +------------------+--------------------------+-------------------+
| 60 | EDITION / ISSUE / VOLUME | RFC 9559, Section | | 60 | EDITION / ISSUE / VOLUME | RFC 9559, Section |
| | / OPUS / SEASON / SEQUEL | 5.1.8.1.1.1 | | | / OPUS / SEASON / SEQUEL | 5.1.8.1.1.1 |
+------------------+--------------------------+-------------------+ +------------------+--------------------------+-------------------+
skipping to change at line 7017 skipping to change at line 7016
Table 58: Initial Contents of "Tags Target Types" Registry Table 58: Initial Contents of "Tags Target Types" Registry
27.5. Alpha Modes Registry 27.5. Alpha Modes Registry
IANA has created a new registry called the "Alpha Modes" registry. IANA has created a new registry called the "Alpha Modes" registry.
The values correspond to the unsigned integer AlphaMode value The values correspond to the unsigned integer AlphaMode value
described in Section 5.1.4.1.28.4. described in Section 5.1.4.1.28.4.
To register a new Alpha Mode in this registry, one needs an Alpha To register a new Alpha Mode in this registry, one needs an Alpha
Mode value, description, a Change Controller (IETF or email of Mode value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the registrant), and an optional Reference to a document describing the
Alpha Mode. Alpha Mode.
The Alpha Modes are to be allocated according to the "First Come The Alpha Modes are to be allocated according to the "First Come
First Served" policy [RFC8126]. First Served" policy [RFC8126].
Table 59 shows the initial contents of the "Alpha Modes" registry. Table 59 shows the initial contents of the "Alpha Modes" registry.
Note that the Change Controller for all entries in Table 59 is The Change Controller for the initial entries is the IETF.
"IETF".
+============+=============+================================+ +============+=============+================================+
| Alpha Mode | Description | Reference | | Alpha Mode | Description | Reference |
+============+=============+================================+ +============+=============+================================+
| 0 | none | RFC 9559, Section 5.1.4.1.28.4 | | 0 | none | RFC 9559, Section 5.1.4.1.28.4 |
+------------+-------------+--------------------------------+ +------------+-------------+--------------------------------+
| 1 | present | RFC 9559, Section 5.1.4.1.28.4 | | 1 | present | RFC 9559, Section 5.1.4.1.28.4 |
+------------+-------------+--------------------------------+ +------------+-------------+--------------------------------+
Table 59: Initial Contents of "Alpha Modes" Registry Table 59: Initial Contents of "Alpha Modes" Registry
27.6. Content Encoding Scopes Registry 27.6. Content Encoding Scopes Registry
IANA has created a new registry called the "Content Encoding Scopes" IANA has created a new registry called the "Content Encoding Scopes"
registry. The values correspond to the unsigned integer registry. The values correspond to the unsigned integer
ContentEncodingScope value described in Section 5.1.4.1.31.3. ContentEncodingScope value described in Section 5.1.4.1.31.3.
To register a new Content Encoding Scope in this registry, one needs To register a new Content Encoding Scope in this registry, one needs
an Content Encoding Scope value, description, a Change Controller a Content Encoding Scope value, a description, a Change Controller
(IETF or email of registrant), and an optional Reference to a (IETF or email of registrant), and an optional Reference to a
document describing the Content Encoding Scope. document describing the Content Encoding Scope.
The Content Encoding Scopes are to be allocated according to the The Content Encoding Scopes are to be allocated according to the
"Specification Required" policy [RFC8126]. "Specification Required" policy [RFC8126].
Table 60 shows the initial contents of the "Content Encoding Scopes" Table 60 shows the initial contents of the "Content Encoding Scopes"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 60 is "IETF".
+========================+=============+===================+ +========================+=============+===================+
| Content Encoding Scope | Description | Reference | | Content Encoding Scope | Description | Reference |
+========================+=============+===================+ +========================+=============+===================+
| 1 | Block | RFC 9559, Section | | 1 | Block | RFC 9559, Section |
| | | 5.1.4.1.31.3 | | | | 5.1.4.1.31.3 |
+------------------------+-------------+-------------------+ +------------------------+-------------+-------------------+
| 2 | Private | RFC 9559, Section | | 2 | Private | RFC 9559, Section |
| | | 5.1.4.1.31.3 | | | | 5.1.4.1.31.3 |
+------------------------+-------------+-------------------+ +------------------------+-------------+-------------------+
skipping to change at line 7078 skipping to change at line 7075
Table 60: Initial Contents of "Content Encoding Scopes" Table 60: Initial Contents of "Content Encoding Scopes"
Registry Registry
27.7. Content Encoding Types Registry 27.7. Content Encoding Types Registry
IANA has created a new registry called the "Content Encoding Types" IANA has created a new registry called the "Content Encoding Types"
registry. The values correspond to the unsigned integer registry. The values correspond to the unsigned integer
ContentEncodingType value described in Section 5.1.4.1.31.4. ContentEncodingType value described in Section 5.1.4.1.31.4.
To register a new Content Encoding Type in this registry, one needs To register a new Content Encoding Type in this registry, one needs a
an Content Encoding Type value, description, a Change Controller Content Encoding Type value, a description, a Change Controller (IETF
(IETF or email of registrant), and an optional Reference to a or email of registrant), and an optional Reference to a document
document describing the Content Encoding Type. describing the Content Encoding Type.
The Content Encoding Types are to be allocated according to the The Content Encoding Types are to be allocated according to the
"Specification Required" policy [RFC8126]. "Specification Required" policy [RFC8126].
Table 61 shows the initial contents of the "Content Encoding Types" Table 61 shows the initial contents of the "Content Encoding Types"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 61 is "IETF".
+=======================+=============+===================+ +=======================+=============+===================+
| Content Encoding Type | Description | Reference | | Content Encoding Type | Description | Reference |
+=======================+=============+===================+ +=======================+=============+===================+
| 0 | Compression | RFC 9559, Section | | 0 | Compression | RFC 9559, Section |
| | | 5.1.4.1.31.4 | | | | 5.1.4.1.31.4 |
+-----------------------+-------------+-------------------+ +-----------------------+-------------+-------------------+
| 1 | Encryption | RFC 9559, Section | | 1 | Encryption | RFC 9559, Section |
| | | 5.1.4.1.31.4 | | | | 5.1.4.1.31.4 |
+-----------------------+-------------+-------------------+ +-----------------------+-------------+-------------------+
Table 61: Initial Contents of "Content Encoding Types" Table 61: Initial Contents of "Content Encoding Types"
Registry Registry
27.8. Compression Algorithms Registry 27.8. Compression Algorithms Registry
IANA has created a new registry called the "Compression Algorithms" IANA has created a new registry called the "Compression Algorithms"
registry. The values correspond to the unsigned integer registry. The values correspond to the unsigned integer
ContentCompAlgo value described in Section 5.1.4.1.31.6. ContentCompAlgo value described in Section 5.1.4.1.31.6.
To register a new Compression Algorithm in this registry, one needs To register a new Compression Algorithm in this registry, one needs a
an Compression Algorithm value, description, a Change Controller Compression Algorithm value, a description, a Change Controller (IETF
(IETF or email of registrant), and an optional Reference to a or email of registrant), and an optional Reference to a document
document describing the Compression Algorithm. describing the Compression Algorithm.
The Compression Algorithms are to be allocated according to the The Compression Algorithms are to be allocated according to the
"Specification Required" policy [RFC8126]. "Specification Required" policy [RFC8126].
Table 62 shows the initial contents of the "Compression Algorithms" Table 62 shows the initial contents of the "Compression Algorithms"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 62 is "IETF".
+=======================+=============+===================+ +=======================+=============+===================+
| Compression Algorithm | Description | Reference | | Compression Algorithm | Description | Reference |
+=======================+=============+===================+ +=======================+=============+===================+
| 0 | zlib | RFC 9559, Section | | 0 | zlib | RFC 9559, Section |
| | | 5.1.4.1.31.6 | | | | 5.1.4.1.31.6 |
+-----------------------+-------------+-------------------+ +-----------------------+-------------+-------------------+
| 1 | bzlib | RFC 9559, Section | | 1 | bzlib | RFC 9559, Section |
| | | 5.1.4.1.31.6 | | | | 5.1.4.1.31.6 |
+-----------------------+-------------+-------------------+ +-----------------------+-------------+-------------------+
skipping to change at line 7147 skipping to change at line 7142
Table 62: Initial Contents of "Compression Algorithms" Table 62: Initial Contents of "Compression Algorithms"
Registry Registry
27.9. Encryption Algorithms Registry 27.9. Encryption Algorithms Registry
IANA has created a new registry called the "Encryption Algorithms" IANA has created a new registry called the "Encryption Algorithms"
registry. The values correspond to the unsigned integer registry. The values correspond to the unsigned integer
ContentEncAlgo value described in Section 5.1.4.1.31.9. ContentEncAlgo value described in Section 5.1.4.1.31.9.
To register a new Encryption Algorithm in this registry, one needs an To register a new Encryption Algorithm in this registry, one needs an
Encryption Algorithm value, description, a Change Controller (IETF or Encryption Algorithm value, a description, a Change Controller (IETF
email of registrant), and an optional Reference to a document or email of registrant), and an optional Reference to a document
describing the Encryption Algorithm. describing the Encryption Algorithm.
The Encryption Algorithms are to be allocated according to the "First The Encryption Algorithms are to be allocated according to the "First
Come First Served" policy [RFC8126]. Come First Served" policy [RFC8126].
Table 63 shows the initial contents of the "Encryption Algorithms" Table 63 shows the initial contents of the "Encryption Algorithms"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 63 is "IETF".
+======================+===============+===================+ +======================+===============+===================+
| Encryption Algorithm | Description | Reference | | Encryption Algorithm | Description | Reference |
+======================+===============+===================+ +======================+===============+===================+
| 0 | Not encrypted | RFC 9559, Section | | 0 | Not encrypted | RFC 9559, Section |
| | | 5.1.4.1.31.9 | | | | 5.1.4.1.31.9 |
+----------------------+---------------+-------------------+ +----------------------+---------------+-------------------+
| 1 | DES | RFC 9559, Section | | 1 | DES | RFC 9559, Section |
| | | 5.1.4.1.31.9 | | | | 5.1.4.1.31.9 |
+----------------------+---------------+-------------------+ +----------------------+---------------+-------------------+
skipping to change at line 7190 skipping to change at line 7184
Table 63: Initial Contents of "Encryption Algorithms" Table 63: Initial Contents of "Encryption Algorithms"
Registry Registry
27.10. AES Cipher Modes Registry 27.10. AES Cipher Modes Registry
IANA has created a new registry called the "AES Cipher Modes" IANA has created a new registry called the "AES Cipher Modes"
registry. The values correspond to the unsigned integer registry. The values correspond to the unsigned integer
AESSettingsCipherMode value described in Section 5.1.4.1.31.12. AESSettingsCipherMode value described in Section 5.1.4.1.31.12.
To register a new AES Cipher Mode in this registry, one needs an AES To register a new AES Cipher Mode in this registry, one needs an AES
Cipher Mode value, description, a Change Controller (IETF or email of Cipher Mode value, a description, a Change Controller (IETF or email
registrant), and an optional Reference to a document describing the of registrant), and an optional Reference to a document describing
AES Cipher Mode. the AES Cipher Mode.
The AES Cipher Modes are to be allocated according to the "First Come The AES Cipher Modes are to be allocated according to the "First Come
First Served" policy [RFC8126]. First Served" policy [RFC8126].
Table 64 shows the initial contents of the "AES Cipher Modes" Table 64 shows the initial contents of the "AES Cipher Modes"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 64 is "IETF".
+=================+=============+=================================+ +=================+=============+=================================+
| AES Cipher Mode | Description | Reference | | AES Cipher Mode | Description | Reference |
+=================+=============+=================================+ +=================+=============+=================================+
| 1 | AES-CTR | RFC 9559, Section 5.1.4.1.31.12 | | 1 | AES-CTR | RFC 9559, Section 5.1.4.1.31.12 |
+-----------------+-------------+---------------------------------+ +-----------------+-------------+---------------------------------+
| 2 | AES-CBC | RFC 9559, Section 5.1.4.1.31.12 | | 2 | AES-CBC | RFC 9559, Section 5.1.4.1.31.12 |
+-----------------+-------------+---------------------------------+ +-----------------+-------------+---------------------------------+
Table 64: Initial Contents of "AES Cipher Modes" Registry Table 64: Initial Contents of "AES Cipher Modes" Registry
27.11. Stereo Modes Registry 27.11. Stereo Modes Registry
IANA has created a new registry called the "Stereo Modes" registry. IANA has created a new registry called the "Stereo Modes" registry.
The values correspond to the unsigned integer StereoMode value The values correspond to the unsigned integer StereoMode value
described in Section 5.1.4.1.28.3. described in Section 5.1.4.1.28.3.
To register a new Stereo Mode in this registry, one needs an Stereo To register a new Stereo Mode in this registry, one needs a Stereo
Mode value, description, a Change Controller (IETF or email of Mode value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the registrant), and an optional Reference to a document describing the
Stereo Mode. Stereo Mode.
The Stereo Modes are to be allocated according to the "Specification The Stereo Modes are to be allocated according to the "Specification
Required" policy [RFC8126]. Required" policy [RFC8126].
Table 65 shows the initial contents of the "Stereo Modes" registry. Table 65 shows the initial contents of the "Stereo Modes" registry.
Note that the Change Controller for all entries in Table 65 is The Change Controller for the initial entries is the IETF.
"IETF".
+=============+====================+================================+ +=============+====================+================================+
| Stereo Mode | Description | Reference | | Stereo Mode | Description | Reference |
+=============+====================+================================+ +=============+====================+================================+
| 0 | mono | RFC 9559, Section | | 0 | mono | RFC 9559, Section |
| | | 5.1.4.1.28.3 | | | | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+ +-------------+--------------------+--------------------------------+
| 1 | Side By Side (left | RFC 9559, Section | | 1 | Side By Side (left | RFC 9559, Section |
| | first) | 5.1.4.1.28.3 | | | first) | 5.1.4.1.28.3 |
+-------------+--------------------+--------------------------------+ +-------------+--------------------+--------------------------------+
skipping to change at line 7286 skipping to change at line 7278
+-------------+--------------------+--------------------------------+ +-------------+--------------------+--------------------------------+
Table 65: Initial Contents of "Stereo Modes" Registry Table 65: Initial Contents of "Stereo Modes" Registry
27.12. Display Units Registry 27.12. Display Units Registry
IANA has created a new registry called the "Display Units" registry. IANA has created a new registry called the "Display Units" registry.
The values correspond to the unsigned integer DisplayUnit value The values correspond to the unsigned integer DisplayUnit value
described in Section 5.1.4.1.28.14. described in Section 5.1.4.1.28.14.
To register a new Display Unit in this registry, one needs an Display To register a new Display Unit in this registry, one needs a Display
Unit value, description, a Change Controller (IETF or email of Unit value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the registrant), and an optional Reference to a document describing the
Display Unit. Display Unit.
The Display Units are to be allocated according to the "Specification The Display Units are to be allocated according to the "Specification
Required" policy [RFC8126]. Required" policy [RFC8126].
Table 66 shows the initial contents of the "Display Units" registry. Table 66 shows the initial contents of the "Display Units" registry.
Note that the Change Controller for all entries in Table 66 is The Change Controller for the initial entries is the IETF.
"IETF".
+==============+===============+=================================+ +==============+===============+=================================+
| Display Unit | Description | Reference | | Display Unit | Description | Reference |
+==============+===============+=================================+ +==============+===============+=================================+
| 0 | Pixels | RFC 9559, Section 5.1.4.1.28.14 | | 0 | Pixels | RFC 9559, Section 5.1.4.1.28.14 |
+--------------+---------------+---------------------------------+ +--------------+---------------+---------------------------------+
| 1 | Centimeters | RFC 9559, Section 5.1.4.1.28.14 | | 1 | Centimeters | RFC 9559, Section 5.1.4.1.28.14 |
+--------------+---------------+---------------------------------+ +--------------+---------------+---------------------------------+
| 2 | Inches | RFC 9559, Section 5.1.4.1.28.14 | | 2 | Inches | RFC 9559, Section 5.1.4.1.28.14 |
+--------------+---------------+---------------------------------+ +--------------+---------------+---------------------------------+
skipping to change at line 7321 skipping to change at line 7312
+--------------+---------------+---------------------------------+ +--------------+---------------+---------------------------------+
Table 66: Initial Contents of "Display Units" Registry Table 66: Initial Contents of "Display Units" Registry
27.13. Projection Types Registry 27.13. Projection Types Registry
IANA has created a new registry called the "Projection Types" IANA has created a new registry called the "Projection Types"
registry. The values correspond to the unsigned integer registry. The values correspond to the unsigned integer
ProjectionType value described in Section 5.1.4.1.28.42. ProjectionType value described in Section 5.1.4.1.28.42.
To register a new Projection Type in this registry, one needs an To register a new Projection Type in this registry, one needs a
Projection Type value, description, a Change Controller (IETF or Projection Type value, a description, a Change Controller (IETF or
email of registrant), and an optional Reference to a document email of registrant), and an optional Reference to a document
describing the Projection Type. describing the Projection Type.
The Projection Types are to be allocated according to the "First Come The Projection Types are to be allocated according to the "First Come
First Served" policy [RFC8126]. First Served" policy [RFC8126].
Table 67 shows the initial contents of the "Projection Types" Table 67 shows the initial contents of the "Projection Types"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 67 is "IETF".
+=================+=================+===================+ +=================+=================+===================+
| Projection Type | Description | Reference | | Projection Type | Description | Reference |
+=================+=================+===================+ +=================+=================+===================+
| 0 | Rectangular | RFC 9559, Section | | 0 | Rectangular | RFC 9559, Section |
| | | 5.1.4.1.28.42 | | | | 5.1.4.1.28.42 |
+-----------------+-----------------+-------------------+ +-----------------+-----------------+-------------------+
| 1 | Equirectangular | RFC 9559, Section | | 1 | Equirectangular | RFC 9559, Section |
| | | 5.1.4.1.28.42 | | | | 5.1.4.1.28.42 |
+-----------------+-----------------+-------------------+ +-----------------+-----------------+-------------------+
skipping to change at line 7357 skipping to change at line 7347
+-----------------+-----------------+-------------------+ +-----------------+-----------------+-------------------+
Table 67: Initial Contents of "Projection Types" Registry Table 67: Initial Contents of "Projection Types" Registry
27.14. Track Plane Types Registry 27.14. Track Plane Types Registry
IANA has created a new registry called the "Track Plane Types" IANA has created a new registry called the "Track Plane Types"
registry. The values correspond to the unsigned integer registry. The values correspond to the unsigned integer
TrackPlaneType value described in Section 5.1.4.1.30.4. TrackPlaneType value described in Section 5.1.4.1.30.4.
To register a new Track Plane Type in this registry, one needs an To register a new Track Plane Type in this registry, one needs a
Track Plane Type value, description, a Change Controller (IETF or Track Plane Type value, a description, a Change Controller (IETF or
email of registrant), and an optional Reference to a document email of registrant), and an optional Reference to a document
describing the Track Plane Type. describing the Track Plane Type.
The Track Plane Types are to be allocated according to the "First The Track Plane Types are to be allocated according to the "First
Come First Served" policy [RFC8126]. Come First Served" policy [RFC8126].
Table 68 shows the initial contents of the "Track Plane Types" Table 68 shows the initial contents of the "Track Plane Types"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 68 is "IETF".
+==================+=============+================================+ +==================+=============+================================+
| Track Plane Type | Description | Reference | | Track Plane Type | Description | Reference |
+==================+=============+================================+ +==================+=============+================================+
| 0 | Left Eye | RFC 9559, Section 5.1.4.1.30.4 | | 0 | Left Eye | RFC 9559, Section 5.1.4.1.30.4 |
+------------------+-------------+--------------------------------+ +------------------+-------------+--------------------------------+
| 1 | Right Eye | RFC 9559, Section 5.1.4.1.30.4 | | 1 | Right Eye | RFC 9559, Section 5.1.4.1.30.4 |
+------------------+-------------+--------------------------------+ +------------------+-------------+--------------------------------+
| 2 | Background | RFC 9559, Section 5.1.4.1.30.4 | | 2 | Background | RFC 9559, Section 5.1.4.1.30.4 |
+------------------+-------------+--------------------------------+ +------------------+-------------+--------------------------------+
Table 68: Initial Contents of "Track Plane Types" Registry Table 68: Initial Contents of "Track Plane Types" Registry
27.15. Horizontal Chroma Sitings Registry 27.15. Horizontal Chroma Sitings Registry
IANA has created a new registry called the "Horizontal Chroma IANA has created a new registry called the "Horizontal Chroma
Sitings" registry. The values correspond to the unsigned integer Sitings" registry. The values correspond to the unsigned integer
ChromaSitingHorz value described in Section 5.1.4.1.28.23. ChromaSitingHorz value described in Section 5.1.4.1.28.23.
To register a new Horizontal Chroma Siting in this registry, one To register a new Horizontal Chroma Siting in this registry, one
needs an Horizontal Chroma Siting value, description, a Change needs a Horizontal Chroma Siting value, a description, a Change
Controller (IETF or email of registrant), and an optional Reference Controller (IETF or email of registrant), and an optional Reference
to a document describing the Horizontal Chroma Siting. to a document describing the Horizontal Chroma Siting.
The Horizontal Chroma Sitings are to be allocated according to the The Horizontal Chroma Sitings are to be allocated according to the
"First Come First Served" policy [RFC8126]. "First Come First Served" policy [RFC8126].
Table 69 shows the initial contents of the "Horizontal Chroma Table 69 shows the initial contents of the "Horizontal Chroma
Sitings" registry. Note that the Change Controller for all entries Sitings" registry. The Change Controller for the initial entries is
in Table 69 is "IETF". the IETF.
+==========================+=============+===================+ +==========================+=============+===================+
| Horizontal Chroma Siting | Description | Reference | | Horizontal Chroma Siting | Description | Reference |
+==========================+=============+===================+ +==========================+=============+===================+
| 0 | unspecified | RFC 9559, Section | | 0 | unspecified | RFC 9559, Section |
| | | 5.1.4.1.28.23 | | | | 5.1.4.1.28.23 |
+--------------------------+-------------+-------------------+ +--------------------------+-------------+-------------------+
| 1 | left | RFC 9559, Section | | 1 | left | RFC 9559, Section |
| | collocated | 5.1.4.1.28.23 | | | collocated | 5.1.4.1.28.23 |
+--------------------------+-------------+-------------------+ +--------------------------+-------------+-------------------+
skipping to change at line 7422 skipping to change at line 7411
Table 69: Initial Contents of "Horizontal Chroma Sitings" Table 69: Initial Contents of "Horizontal Chroma Sitings"
Registry Registry
27.16. Vertical Chroma Sitings Registry 27.16. Vertical Chroma Sitings Registry
IANA has created a new registry called the "Vertical Chroma Sitings" IANA has created a new registry called the "Vertical Chroma Sitings"
registry. The values correspond to the unsigned integer registry. The values correspond to the unsigned integer
ChromaSitingVert value described in Section 5.1.4.1.28.24. ChromaSitingVert value described in Section 5.1.4.1.28.24.
To register a new Vertical Chroma Siting in this registry, one needs To register a new Vertical Chroma Siting in this registry, one needs
an Vertical Chroma Siting value, description, a Change Controller a Vertical Chroma Siting value, a description, a Change Controller
(IETF or email of registrant), and an optional Reference to a (IETF or email of registrant), and an optional Reference to a
document describing the Vertical Chroma Siting. document describing the Vertical Chroma Siting.
The Vertical Chroma Sitings are to be allocated according to the The Vertical Chroma Sitings are to be allocated according to the
"First Come First Served" policy [RFC8126]. "First Come First Served" policy [RFC8126].
Table 70 shows the initial contents of the "Vertical Chroma Sitings" Table 70 shows the initial contents of the "Vertical Chroma Sitings"
registry. Note that the Change Controller for all entries in registry. The Change Controller for the initial entries is the IETF.
Table 70 is "IETF".
+========================+=============+===================+ +========================+=============+===================+
| Vertical Chroma Siting | Description | Reference | | Vertical Chroma Siting | Description | Reference |
+========================+=============+===================+ +========================+=============+===================+
| 0 | unspecified | RFC 9559, Section | | 0 | unspecified | RFC 9559, Section |
| | | 5.1.4.1.28.24 | | | | 5.1.4.1.28.24 |
+------------------------+-------------+-------------------+ +------------------------+-------------+-------------------+
| 1 | top | RFC 9559, Section | | 1 | top | RFC 9559, Section |
| | collocated | 5.1.4.1.28.24 | | | collocated | 5.1.4.1.28.24 |
+------------------------+-------------+-------------------+ +------------------------+-------------+-------------------+
skipping to change at line 7455 skipping to change at line 7443
Table 70: Initial Contents of "Vertical Chroma Sitings" Table 70: Initial Contents of "Vertical Chroma Sitings"
Registry Registry
27.17. Color Ranges Registry 27.17. Color Ranges Registry
IANA has created a new registry called the "Color Ranges" registry. IANA has created a new registry called the "Color Ranges" registry.
The values correspond to the unsigned integer Range value described The values correspond to the unsigned integer Range value described
in Section 5.1.4.1.28.25. in Section 5.1.4.1.28.25.
To register a new Color Range in this registry, one needs an Color To register a new Color Range in this registry, one needs a Color
Range value, description, a Change Controller (IETF or email of Range value, a description, a Change Controller (IETF or email of
registrant), and an optional Reference to a document describing the registrant), and an optional Reference to a document describing the
Color Range. Color Range.
The Color Ranges are to be allocated according to the "Specification The Color Ranges are to be allocated according to the "Specification
Required" policy [RFC8126]. Required" policy [RFC8126].
Table 71 shows the initial contents of the "Color Ranges" registry. Table 71 shows the initial contents of the "Color Ranges" registry.
Note that the Change Controller for all entries in Table 71 is The Change Controller for the initial entries is the IETF.
"IETF".
+=============+===============================+===================+ +=============+===============================+===================+
| Color Range | Description | Reference | | Color Range | Description | Reference |
+=============+===============================+===================+ +=============+===============================+===================+
| 0 | unspecified | RFC 9559, Section | | 0 | unspecified | RFC 9559, Section |
| | | 5.1.4.1.28.25 | | | | 5.1.4.1.28.25 |
+-------------+-------------------------------+-------------------+ +-------------+-------------------------------+-------------------+
| 1 | broadcast range | RFC 9559, Section | | 1 | broadcast range | RFC 9559, Section |
| | | 5.1.4.1.28.25 | | | | 5.1.4.1.28.25 |
+-------------+-------------------------------+-------------------+ +-------------+-------------------------------+-------------------+
skipping to change at line 7502 skipping to change at line 7489
SHOULD be able to handle both formats. Newer systems SHOULD NOT use SHOULD be able to handle both formats. Newer systems SHOULD NOT use
the historic format and use the format that follows the format in the historic format and use the format that follows the format in
[RFC6838] instead. [RFC6838] instead.
IANA has registered three media types per the templates (see IANA has registered three media types per the templates (see
[RFC6838]) in the following subsections. [RFC6838]) in the following subsections.
27.18.1. For Files Containing Video Tracks 27.18.1. For Files Containing Video Tracks
Type name: video Type name: video
Subtype name: matroska Subtype name: matroska
Required parameters: N/A Required parameters: N/A
Optional parameters: N/A Optional parameters: N/A
Encoding considerations: As per RFCs 9559 and 8794 Encoding considerations: As per RFCs 9559 and 8794
Security considerations: See Section 26 of RFC 9559. Security considerations: See Section 26 of RFC 9559.
Interoperability considerations: Due to the extensibility of Interoperability considerations: Due to the extensibility of
Matroska, it is possible to encounter files with unknown but valid Matroska, it is possible to encounter files with unknown but valid
EBML Elements. Readers should be ready to handle this case. The EBML Elements. Readers should be ready to handle this case. The
fixed byte order, octet boundaries, and UTF-8 usage allow for fixed byte order, octet boundaries, and UTF-8 usage allow for
broad interoperability. broad interoperability.
Published specification: RFC 9559 Published specification: RFC 9559
Applications that use this media type: FFmpeg, VLC, etc. Applications that use this media type: FFmpeg, VLC, etc.
Fragment identifier considerations: N/A Fragment identifier considerations: N/A
Additional information: Additional information:
Deprecated alias names for this type: video/x-matroska Deprecated alias names for this type: video/x-matroska
Magic number(s): N/A Magic number(s): N/A
File extension(s): mkv File extension(s): mkv
Macintosh file type code(s): N/A Macintosh file type code(s): N/A
Person & email address to contact for further information: IETF Person & email address to contact for further information: IETF
CELLAR WG (cellar@ietf.org) CELLAR WG (cellar@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: None Restrictions on usage: None
Author: IETF CELLAR WG Author: IETF CELLAR WG
Change controller: IETF Change controller: IETF
27.18.2. For Files Containing Audio Tracks with No Video Tracks 27.18.2. For Files Containing Audio Tracks with No Video Tracks
Type name: audio Type name: audio
Subtype name: matroska Subtype name: matroska
Required parameters: N/A Required parameters: N/A
Optional parameters: N/A Optional parameters: N/A
Encoding considerations: As per RFCs 9559 and 8794 Encoding considerations: As per RFCs 9559 and 8794
Security considerations: See Section 26 of RFC 9559. Security considerations: See Section 26 of RFC 9559.
Interoperability considerations: Due to the extensibility of Interoperability considerations: Due to the extensibility of
Matroska, it is possible to encounter files with unknown but valid Matroska, it is possible to encounter files with unknown but valid
EBML Elements. Readers should be ready to handle this case. The EBML Elements. Readers should be ready to handle this case. The
fixed byte order, octet boundaries, and UTF-8 usage allow for fixed byte order, octet boundaries, and UTF-8 usage allow for
broad interoperability. broad interoperability.
Published specification: RFC 9559 Published specification: RFC 9559
Applications that use this media type: FFmpeg, VLC, etc. Applications that use this media type: FFmpeg, VLC, etc.
Fragment identifier considerations: N/A Fragment identifier considerations: N/A
Additional information: Additional information:
Deprecated alias names for this type: audio/x-matroska Deprecated alias names for this type: audio/x-matroska
Magic number(s): N/A Magic number(s): N/A
File extension(s): mka File extension(s): mka
Macintosh file type code(s): N/A Macintosh file type code(s): N/A
Person & email address to contact for further information: IETF Person & email address to contact for further information: IETF
CELLAR WG (cellar@ietf.org) CELLAR WG (cellar@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: None Restrictions on usage: None
Author: IETF CELLAR WG Author: IETF CELLAR WG
Change controller: IETF Change controller: IETF
27.18.3. For Files Containing a Stereoscopic Video Track 27.18.3. For Files Containing a Stereoscopic Video Track
Type name: video Type name: video
Subtype name: matroska-3d Subtype name: matroska-3d
Required parameters: N/A Required parameters: N/A
Optional parameters: N/A Optional parameters: N/A
Encoding considerations: As per RFCs 9559 and 8794 Encoding considerations: As per RFCs 9559 and 8794
Security considerations: See Section 26 of RFC 9559. Security considerations: See Section 26 of RFC 9559.
Interoperability considerations: Due to the extensibility of Interoperability considerations: Due to the extensibility of
Matroska, it is possible to encounter files with unknown but valid Matroska, it is possible to encounter files with unknown but valid
EBML Elements. Readers should be ready to handle this case. The EBML Elements. Readers should be ready to handle this case. The
fixed byte order, octet boundaries, and UTF-8 usage allow for fixed byte order, octet boundaries, and UTF-8 usage allow for
broad interoperability. broad interoperability.
Published specification: RFC 9559 Published specification: RFC 9559
Applications that use this media type: FFmpeg, VLC, etc. Applications that use this media type: FFmpeg, VLC, etc.
Fragment identifier considerations: N/A Fragment identifier considerations: N/A
Additional information: Additional information:
Deprecated alias names for this type: video/x-matroska-3d Deprecated alias names for this type: video/x-matroska-3d
Magic number(s): N/A Magic number(s): N/A
File extension(s): mk3d File extension(s): mk3d
Macintosh file type code(s): N/A Macintosh file type code(s): N/A
Person & email address to contact for further information: IETF Person & email address to contact for further information: IETF
CELLAR WG (cellar@ietf.org) CELLAR WG (cellar@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: None Restrictions on usage: None
Author: IETF CELLAR WG Author: IETF CELLAR WG
Change controller: IETF Change controller: IETF
28. References 28. References
28.1. Normative References 28.1. Normative References
[CIE-1931] Wikipedia, "CIE 1931 color space", [CIE-1931] Wikipedia, "CIE 1931 color space",
<https://en.wikipedia.org/wiki/CIE_1931_color_space>. <https://en.wikipedia.org/wiki/CIE_1931_color_space>.
[ISO639-2] International Organization for Standardization, "Codes for [ISO639-2] International Organization for Standardization, "Codes for
 End of changes. 95 change blocks. 
121 lines changed or deleted 150 lines changed or added

This html diff was produced by rfcdiff 1.48.