draft-ietf-cellar-ebml-06.txt   draft-ietf-cellar-ebml-07.txt 
cellar S. Lhomme cellar S. Lhomme
Internet-Draft Internet-Draft
Intended status: Standards Track D. Rice Intended status: Standards Track D. Rice
Expires: March 1, 2019 Expires: March 29, 2019
M. Bunkus M. Bunkus
August 28, 2018 September 25, 2018
Extensible Binary Meta Language Extensible Binary Meta Language
draft-ietf-cellar-ebml-06 draft-ietf-cellar-ebml-07
Abstract Abstract
This document defines the Extensible Binary Meta Language (EBML) This document defines the Extensible Binary Meta Language (EBML)
format as a generalized file format for any type of data in a format as a generalized file format for any type of data in a
hierarchical form. EBML is designed as a binary equivalent to XML hierarchical form. EBML is designed as a binary equivalent to XML
and uses a storage-efficient approach to build nested Elements with and uses a storage-efficient approach to build nested Elements with
identifiers, lengths, and values. Similar to how an XML Schema identifiers, lengths, and values. Similar to how an XML Schema
defines the structure and semantics of an XML Document, this document defines the structure and semantics of an XML Document, this document
defines how EBML Schemas are created to convey the semantics of an defines how EBML Schemas are created to convey the semantics of an
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 1, 2019. This Internet-Draft will expire on March 29, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 45 skipping to change at page 2, line 45
10.1.1. Adding a Void Element . . . . . . . . . . . . . . . 16 10.1.1. Adding a Void Element . . . . . . . . . . . . . . . 16
10.1.2. Extending the Element Data Size . . . . . . . . . . 16 10.1.2. Extending the Element Data Size . . . . . . . . . . 16
10.1.3. Terminating Element Data . . . . . . . . . . . . . . 17 10.1.3. Terminating Element Data . . . . . . . . . . . . . . 17
10.2. Considerations when Updating Elements with CRC . . . . . 17 10.2. Considerations when Updating Elements with CRC . . . . . 17
11. EBML Document . . . . . . . . . . . . . . . . . . . . . . . . 18 11. EBML Document . . . . . . . . . . . . . . . . . . . . . . . . 18
11.1. EBML Header . . . . . . . . . . . . . . . . . . . . . . 18 11.1. EBML Header . . . . . . . . . . . . . . . . . . . . . . 18
11.2. EBML Body . . . . . . . . . . . . . . . . . . . . . . . 18 11.2. EBML Body . . . . . . . . . . . . . . . . . . . . . . . 18
12. EBML Stream . . . . . . . . . . . . . . . . . . . . . . . . . 19 12. EBML Stream . . . . . . . . . . . . . . . . . . . . . . . . . 19
13. Elements semantic . . . . . . . . . . . . . . . . . . . . . . 19 13. Elements semantic . . . . . . . . . . . . . . . . . . . . . . 19
13.1. EBML Schema . . . . . . . . . . . . . . . . . . . . . . 19 13.1. EBML Schema . . . . . . . . . . . . . . . . . . . . . . 19
13.1.1. Element . . . . . . . . . . . . . . . . . . . . . . 20 13.1.1. <EBMLSchema> Element . . . . . . . . . . . . . . . . 20
13.1.2. Attributes . . . . . . . . . . . . . . . . . . . . . 20 13.1.2. <EBMLSchema> Attributes . . . . . . . . . . . . . . 20
13.1.3. Element . . . . . . . . . . . . . . . . . . . . . . 20 13.1.3. <element> Element . . . . . . . . . . . . . . . . . 20
13.1.4. Attributes . . . . . . . . . . . . . . . . . . . . . 21 13.1.4. <element> Attributes . . . . . . . . . . . . . . . . 21
13.1.5. Element . . . . . . . . . . . . . . . . . . . . . . 26 13.1.5. <documentation> Element . . . . . . . . . . . . . . 26
13.1.6. Attributes . . . . . . . . . . . . . . . . . . . . . 26 13.1.6. <documentation> Attributes . . . . . . . . . . . . . 26
13.1.7. Element . . . . . . . . . . . . . . . . . . . . . . 26 13.1.7. <restriction> Element . . . . . . . . . . . . . . . 26
13.1.8. Element . . . . . . . . . . . . . . . . . . . . . . 26 13.1.8. <enum> Element . . . . . . . . . . . . . . . . . . . 26
13.1.9. Attributes . . . . . . . . . . . . . . . . . . . . . 26 13.1.9. <enum> Attributes . . . . . . . . . . . . . . . . . 26
13.1.10. XML Schema for EBML Schema . . . . . . . . . . . . . 27 13.1.10. XML Schema for EBML Schema . . . . . . . . . . . . . 27
13.1.11. EBML Schema Example . . . . . . . . . . . . . . . . 28 13.1.11. EBML Schema Example . . . . . . . . . . . . . . . . 28
13.1.12. Identically Recurring Elements . . . . . . . . . . . 29 13.1.12. Identically Recurring Elements . . . . . . . . . . . 29
13.1.13. Expression of range . . . . . . . . . . . . . . . . 30 13.1.13. Expression of range . . . . . . . . . . . . . . . . 30
13.1.14. Textual expression of floats . . . . . . . . . . . . 30 13.1.14. Textual expression of floats . . . . . . . . . . . . 30
13.1.15. Note on the use of default attributes to define 13.1.15. Note on the use of default attributes to define
Mandatory EBML Elements . . . . . . . . . . . . . . 31 Mandatory EBML Elements . . . . . . . . . . . . . . 31
13.2. EBML Header Elements . . . . . . . . . . . . . . . . . . 32 13.2. EBML Header Elements . . . . . . . . . . . . . . . . . . 32
13.2.1. EBML Element . . . . . . . . . . . . . . . . . . . . 32 13.2.1. EBML Element . . . . . . . . . . . . . . . . . . . . 32
13.2.2. EBMLVersion Element . . . . . . . . . . . . . . . . 32 13.2.2. EBMLVersion Element . . . . . . . . . . . . . . . . 32
13.2.3. EBMLReadVersion Element . . . . . . . . . . . . . . 33 13.2.3. EBMLReadVersion Element . . . . . . . . . . . . . . 33
13.2.4. EBMLMaxIDLength Element . . . . . . . . . . . . . . 33 13.2.4. EBMLMaxIDLength Element . . . . . . . . . . . . . . 33
13.2.5. EBMLMaxSizeLength Element . . . . . . . . . . . . . 34 13.2.5. EBMLMaxSizeLength Element . . . . . . . . . . . . . 34
13.2.6. DocType Element . . . . . . . . . . . . . . . . . . 34 13.2.6. DocType Element . . . . . . . . . . . . . . . . . . 34
13.2.7. DocTypeVersion Element . . . . . . . . . . . . . . . 35 13.2.7. DocTypeVersion Element . . . . . . . . . . . . . . . 35
13.2.8. DocTypeReadVersion Element . . . . . . . . . . . . . 35 13.2.8. DocTypeReadVersion Element . . . . . . . . . . . . . 35
13.3. Global Elements . . . . . . . . . . . . . . . . . . . . 36 13.2.9. DocTypeExtension Element . . . . . . . . . . . . . . 36
13.3.1. CRC-32 Element . . . . . . . . . . . . . . . . . . . 36 13.2.10. DocTypeExtensionName Element . . . . . . . . . . . . 36
13.3.2. Void Element . . . . . . . . . . . . . . . . . . . . 36 13.2.11. DocTypeExtensionVersion Element . . . . . . . . . . 36
14. Considerations for Reading EBML Data . . . . . . . . . . . . 37 13.3. Global Elements . . . . . . . . . . . . . . . . . . . . 37
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 13.3.1. CRC-32 Element . . . . . . . . . . . . . . . . . . . 37
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 38 13.3.2. Void Element . . . . . . . . . . . . . . . . . . . . 38
16.1. Normative References . . . . . . . . . . . . . . . . . . 38 14. Considerations for Reading EBML Data . . . . . . . . . . . . 38
16.2. Informative References . . . . . . . . . . . . . . . . . 40 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 15.1. CELLAR EBML Element ID Registry . . . . . . . . . . . . 38
15.2. CELLAR EBML DocType Registry . . . . . . . . . . . . . . 40
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 41
16.1. Normative References . . . . . . . . . . . . . . . . . . 41
16.2. Informative References . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42
1. Introduction 1. Introduction
"EBML", short for Extensible Binary Meta Language, specifies a binary "EBML", short for Extensible Binary Meta Language, specifies a binary
and octet (byte) aligned format inspired by the principle of XML (a and octet (byte) aligned format inspired by the principle of XML (a
framework for structuring data). framework for structuring data).
The goal of this document is to define a generic, binary, space- The goal of this document is to define a generic, binary, space-
efficient format that can be used to define more complex formats efficient format that can be used to define more complex formats
(such as containers for multimedia content) using an "EBML Schema". (such as containers for multimedia content) using an "EBML Schema".
skipping to change at page 20, line 5 skipping to change at page 20, line 5
attribute. For example, an "EBML Schema" MAY constrain the attribute. For example, an "EBML Schema" MAY constrain the
"EBMLMaxSizeLength" to a maximum value of "8" or MAY constrain the "EBMLMaxSizeLength" to a maximum value of "8" or MAY constrain the
"EBMLVersion" to only support a value of "1". If an "EBML Schema" "EBMLVersion" to only support a value of "1". If an "EBML Schema"
adopts the "EBML Header Element" as-is, then it is not REQUIRED to adopts the "EBML Header Element" as-is, then it is not REQUIRED to
document that Element within the "EBML Schema". If an "EBML Schema" document that Element within the "EBML Schema". If an "EBML Schema"
constrains the range of an "EBML Header Element", then that "Element" constrains the range of an "EBML Header Element", then that "Element"
MUST be documented within an "<element>" node of the "EBML Schema". MUST be documented within an "<element>" node of the "EBML Schema".
This document provides an example of an "EBML Schema", see This document provides an example of an "EBML Schema", see
Section 13.1.11. Section 13.1.11.
13.1.1. Element 13.1.1. <EBMLSchema> Element
As an XML Document, the "EBML Schema" MUST use "<EBMLSchema>" as the As an XML Document, the "EBML Schema" MUST use "<EBMLSchema>" as the
top level element. The "<EBMLSchema>" element MAY contain top level element. The "<EBMLSchema>" element MAY contain
"<element>" sub-elements. "<element>" sub-elements.
13.1.2. Attributes 13.1.2. <EBMLSchema> Attributes
Within an "EBML Schema" the "<EBMLSchema>" element uses the following Within an "EBML Schema" the "<EBMLSchema>" element uses the following
attributes: attributes:
13.1.2.1. docType 13.1.2.1. docType
The "docType" lists the official name of the "EBML Document Type" The "docType" lists the official name of the "EBML Document Type"
that is defined by the "EBML Schema"; for example, "<EBMLSchema that is defined by the "EBML Schema"; for example, "<EBMLSchema
docType="matroska">". docType="matroska">".
skipping to change at page 20, line 38 skipping to change at page 20, line 38
specifies the version of the docType documented by the "EBML Schema". specifies the version of the docType documented by the "EBML Schema".
Unlike XML Schemas, an "EBML Schema" documents all versions of a Unlike XML Schemas, an "EBML Schema" documents all versions of a
docType's definition rather than using separate "EBML Schemas" for docType's definition rather than using separate "EBML Schemas" for
each version of a "docType". "EBML Elements" may be introduced and each version of a "docType". "EBML Elements" may be introduced and
deprecated by using the "minver" and "maxver" attributes of deprecated by using the "minver" and "maxver" attributes of
"<element>". "<element>".
The "version" attribute is REQUIRED within the "<EBMLSchema>" The "version" attribute is REQUIRED within the "<EBMLSchema>"
Element. Element.
13.1.3. Element 13.1.3. <element> Element
Each "<element>" defines one "EBML Element" through the use of Each "<element>" defines one "EBML Element" through the use of
several attributes that are defined in Section 13.1.2. "EBML several attributes that are defined in Section 13.1.2. "EBML
Schemas" MAY contain additional attributes to extend the semantics Schemas" MAY contain additional attributes to extend the semantics
but MUST NOT conflict with the definitions of the "<element>" but MUST NOT conflict with the definitions of the "<element>"
attributes defined within this document. attributes defined within this document.
The "<element>" nodes contain a description of the meaning and use of The "<element>" nodes contain a description of the meaning and use of
the "EBML Element" stored within one or many "<documentation>" sub- the "EBML Element" stored within one or many "<documentation>" sub-
elements and zero or one "<restriction>" sub-element. All elements and zero or one "<restriction>" sub-element. All
"<element>" nodes MUST be sub-elements of the "<EBMLSchema>". "<element>" nodes MUST be sub-elements of the "<EBMLSchema>".
13.1.4. Attributes 13.1.4. <element> Attributes
Within an "EBML Schema" the "<element>" uses the following attributes Within an "EBML Schema" the "<element>" uses the following attributes
to define an "EBML Element": to define an "EBML Element":
13.1.4.1. name 13.1.4.1. name
The "name" provides the official human-readable name of the "EBML The "name" provides the official human-readable name of the "EBML
Element". The value of the name MUST be in the form of characters Element". The value of the name MUST be in the form of characters
"A" to "Z", "a" to "z", "0" to "9", "-" and ".". "A" to "Z", "a" to "z", "0" to "9", "-" and ".".
skipping to change at page 26, line 5 skipping to change at page 26, line 5
The "maxver" (maximum version) attribute stores a non-negative The "maxver" (maximum version) attribute stores a non-negative
integer that represents the last or most recent version of the integer that represents the last or most recent version of the
"docType" to support the element. "maxver" MUST be greater than or "docType" to support the element. "maxver" MUST be greater than or
equal to "minver". equal to "minver".
The "maxver" attribute is OPTIONAL. If the "maxver" attribute is not The "maxver" attribute is OPTIONAL. If the "maxver" attribute is not
present then the "EBML Element" has a maximum version equal to the present then the "EBML Element" has a maximum version equal to the
value stored in the "version" attribute of "<EBMLSchema>". value stored in the "version" attribute of "<EBMLSchema>".
13.1.5. Element 13.1.5. <documentation> Element
The "<documentation>" element provides additional information about The "<documentation>" element provides additional information about
the "EBML Element". the "EBML Element".
13.1.6. Attributes 13.1.6. <documentation> Attributes
13.1.6.1. lang 13.1.6.1. lang
A "lang" attribute which is set to the [RFC5646] value of the A "lang" attribute which is set to the [RFC5646] value of the
language of the element's documentation. language of the element's documentation.
The "lang" attribute is OPTIONAL. The "lang" attribute is OPTIONAL.
13.1.6.2. type 13.1.6.2. type
A "type" attribute distinguishes the meaning of the documentation. A "type" attribute distinguishes the meaning of the documentation.
Values for the "<documentation>" sub-element's "type" attribute MUST Values for the "<documentation>" sub-element's "type" attribute MUST
include one of the following: "definition", "rationale", "usage include one of the following: "definition", "rationale", "usage
notes", and "references". notes", and "references".
The "type" attribute is OPTIONAL. The "type" attribute is OPTIONAL.
13.1.7. Element 13.1.7. <restriction> Element
The "<restriction>" element provides information about restrictions The "<restriction>" element provides information about restrictions
to the allowable values for the "EBML Element" which are listed in to the allowable values for the "EBML Element" which are listed in
"<enum>" elements. "<enum>" elements.
13.1.8. Element 13.1.8. <enum> Element
The "<enum>" element stores a list of values allowed for storage in The "<enum>" element stores a list of values allowed for storage in
the "EBML Element". The values MUST match the "type" of the "EBML the "EBML Element". The values MUST match the "type" of the "EBML
Element" (for example "<enum value="Yes">" cannot be a valid value Element" (for example "<enum value="Yes">" cannot be a valid value
for a "EBML Element" that is defined as an unsigned integer). An for a "EBML Element" that is defined as an unsigned integer). An
"<enum>" element MAY also store "<documentation>" elements to further "<enum>" element MAY also store "<documentation>" elements to further
describe the "<enum>". describe the "<enum>".
13.1.9. Attributes 13.1.9. <enum> Attributes
13.1.9.1. label 13.1.9.1. label
The "label" provides a concise expression for human consumption that The "label" provides a concise expression for human consumption that
describes what the "value" of the "<enum>" represents. describes what the "value" of the "<enum>" represents.
The "label" attribute is OPTIONAL. The "label" attribute is OPTIONAL.
13.1.9.2. value 13.1.9.2. value
skipping to change at page 36, line 5 skipping to change at page 36, line 5
default: 1 default: 1
type: Unsigned Integer type: Unsigned Integer
description: The minimum "DocType" version an "EBML Reader" has to description: The minimum "DocType" version an "EBML Reader" has to
support to read this "EBML Document". The value of the support to read this "EBML Document". The value of the
"DocTypeReadVersion Element" MUST be less than or equal to the value "DocTypeReadVersion Element" MUST be less than or equal to the value
of the "DocTypeVersion Element". of the "DocTypeVersion Element".
13.2.9. DocTypeExtension Element
name: "DocTypeExtension"
path: "0*(\EBML\DocTypeExtension)"
id "0x4281"
minOccurs: 0
type: "Master Element"
description: A "DocTypeExtension" adds extra "Elements" to the main
"DocType"+"DocTypeVersion" tuple it's attached to. An "EBML Reader"
MAY understand these extra "Elements". A "DocTypeExtension" MAY be
used to iterate between experimental "Elements" before they are
integrated in a regular "DocTypeVersion". Reading one
"DocTypeExtension" version of a "DocType"+"DocTypeVersion" tuple
doesn't imply one should be able to read upper values of this
"DocTypeExtension".
13.2.10. DocTypeExtensionName Element
name: "DocTypeExtensionName"
path: "1*1(\EBML\DocTypeExtension\Name)"
id "0x4283"
minOccurs: 1
maxOccurs: 1
size: >0
type: String
description: The name of the "DocTypeExtension" to identify it from
other "DocTypeExtension" of the same "DocType"+"DocTypeVersion"
tuple.
13.2.11. DocTypeExtensionVersion Element
name: "DocTypeExtensionVersion"
path: "1*1(\EBML\DocTypeExtension\Version)"
id "0x4284"
minOccurs: 1
maxOccurs: 1
range: not 0
type: Unsigned Integer
description: The version of the "DocTypeExtension". Different
"DocTypeExtensionVersion" values of the same
"DocType"+"DocTypeVersion"+"DocTypeExtensionName" tuple MAY contain
completely different sets of extra "Elements". An "EBML Reader" MAY
support multiple versions of the same "DocTypeExtension", only one or
none.
13.3. Global Elements 13.3. Global Elements
EBML defines these "Global Elements" which MAY be stored within any EBML defines these "Global Elements" which MAY be stored within any
"Master Element" of an "EBML Document" as defined by their "Element "Master Element" of an "EBML Document" as defined by their "Element
Path". Path".
13.3.1. CRC-32 Element 13.3.1. CRC-32 Element
name: CRC-32 name: CRC-32
skipping to change at page 37, line 31 skipping to change at page 38, line 44
in addition to "maxOccurs" MAY be ignored. in addition to "maxOccurs" MAY be ignored.
If a "Master Element" contains more occurrences of a "Child Element" If a "Master Element" contains more occurrences of a "Child Element"
that is not a "Master Element" than permitted according to the that is not a "Master Element" than permitted according to the
"maxOccurs" attribute of the definition of that "Element" then all "maxOccurs" attribute of the definition of that "Element" then all
but the instance of that "Element" with the smallest byte offset from but the instance of that "Element" with the smallest byte offset from
the beginning of its "Parent Element" SHOULD be ignored. the beginning of its "Parent Element" SHOULD be ignored.
15. IANA Considerations 15. IANA Considerations
15.1. CELLAR EBML Element ID Registry
This document creates a new IANA Registry called "CELLAR EBML Element This document creates a new IANA Registry called "CELLAR EBML Element
ID Registry". ID Registry".
Element IDs are described in section "Element ID". Element IDs are Element IDs are described in section "Element ID". Element IDs are
encoded using the VINT mechanism described in section Section 5 can encoded using the VINT mechanism described in section Section 5 can
be between one and five octets long. Five octet long Element IDs are be between one and five octets long. Five octet long Element IDs are
possible only if declared in the header. possible only if declared in the header.
This IANA Registry only applies to "Elements" contained at least in
the "EBML Header", thus including "Global Elements". "Elements" only
found in the "EBML Body" have their own set of independent "Element
IDs" and are not part of this IANA Registry.
The VINT Data value of one-octet Element IDs MUST be between 0x01 and The VINT Data value of one-octet Element IDs MUST be between 0x01 and
0x7E. These items are valuable because they are short, and need to 0x7E. These items are valuable because they are short, and need to
be used for commonly repeated elements. Values from 1 to 126 are to be used for commonly repeated elements. Values from 1 to 126 are to
be allocated according to RFC Required. be allocated according to RFC Required.
The VINT Data value of two-octet Element IDs MUST be between 0x007F The VINT Data value of two-octet Element IDs MUST be between 0x007F
and 0x3FFE. Numbers MAY be allocated within this range according to and 0x3FFE. Numbers MAY be allocated within this range according to
Specification Required. Specification Required.
The numbers 0x3FFF and 0x4000 are RESERVED. The numbers 0x3FFF and 0x4000 are RESERVED.
skipping to change at page 38, line 25 skipping to change at page 39, line 41
two categories. Four octet Element IDs whose lower three octets (as two categories. Four octet Element IDs whose lower three octets (as
encoded) would make printable 7-bit ASCII values may be allocated encoded) would make printable 7-bit ASCII values may be allocated
only Specification Required. Sequential allocation of values is not only Specification Required. Sequential allocation of values is not
required: specifications SHOULD include a specific request, and are required: specifications SHOULD include a specific request, and are
encouraged to do early allocations. encouraged to do early allocations.
To be clear about the above category: four octet Element IDs always To be clear about the above category: four octet Element IDs always
start with hex 0x10 to 0x1F, and that octet may be chosen so that the start with hex 0x10 to 0x1F, and that octet may be chosen so that the
entire number has some desirable property, such as a specific CRC. entire number has some desirable property, such as a specific CRC.
The other three octets, when ALL having values between 0x21 (33, The other three octets, when ALL having values between 0x21 (33,
ASCII !) and 0x7e (126, ASCII ~), fall into this catgory. ASCII !) and 0x7e (126, ASCII ~), fall into this category.
Other four octet Element IDs may be allocated by First Come First Other four octet Element IDs may be allocated by First Come First
Served (see [RFC8126]). Served (see [RFC8126]).
The numbers 0xFFFFFFF and 0x1000000 are RESERVED. The numbers 0xFFFFFFF and 0x1000000 are RESERVED.
Five octet Element IDs (values from 0x10000001 upwards) are reserved Five octet Element IDs (values from 0x10000001 upwards) are reserved
for Experimental use: they may be used by anyone at any time, but for Experimental use: they may be used by anyone at any time, but
there is no coordination. there is no coordination.
ID Values found in this document are assigned as initial values as
follows:
+------------+-------------------------+----------------------------+
| ID | Element Name | Reference |
+------------+-------------------------+----------------------------+
| 0x1A45DFA3 | EBML | Described in Section |
| | | 13.2.1 |
| 0x4286 | EBMLVersion | Described in Section |
| | | 13.2.2 |
| 0x42F7 | EBMLReadVersion | Described in Section |
| | | 13.2.3 |
| 0x42F2 | EBMLMaxIDLength | Described in Section |
| | | 13.2.4 |
| 0x42F3 | EBMLMaxSizeLength | Described in Section |
| | | 13.2.5 |
| 0x4282 | DocType | Described in Section |
| | | 13.2.6 |
| 0x4287 | DocTypeVersion | Described in Section |
| | | 13.2.7 |
| 0x4285 | DocTypeReadVersion | Described in Section |
| | | 13.2.8 |
| 0x4281 | DocTypeExtension | Described in Section |
| | | 13.2.9 |
| 0x4283 | DocTypeExtensionName | Described in Section |
| | | 13.2.10 |
| 0x4284 | DocTypeExtensionVersion | Described in Section |
| | | 13.2.11 |
| 0xBF | CRC-32 | Described in Section |
| | | 13.3.1 |
| 0xEC | Void | Described in Section |
| | | 13.3.2 |
+------------+-------------------------+----------------------------+
15.2. CELLAR EBML DocType Registry
This document creates a new IANA Registry called "CELLAR EBML DocType
Registry".
DocType values are described in Section 13.1.2.1. DocTypes are ASCII
strings, defined in Section 8.4, which label the official name of the
"EBML Document Type". The strings may be allocated according to
First Come First Served (see [RFC8126]).
The use of ASCII corresponds to the types and code already in use,
the value is not meant to be visible to the user.
DocType string values of "matroska" and "webm" are reserved for pre-
existing formats.
16. References 16. References
16.1. Normative References 16.1. Normative References
[IEEE.754.1985] [IEEE.754.1985]
Institute of Electrical and Electronics Engineers, Institute of Electrical and Electronics Engineers,
"Standard for Binary Floating-Point Arithmetic", "Standard for Binary Floating-Point Arithmetic",
IEEE Standard 754, August 1985. IEEE Standard 754, August 1985.
[ISO.3309.1979] [ISO.3309.1979]
 End of changes. 20 change blocks. 
32 lines changed or deleted 157 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/