draft-ietf-cellar-ebml-07.txt   draft-ietf-cellar-ebml-08.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 29, 2019 Expires: May 31, 2019
M. Bunkus M. Bunkus
September 25, 2018 November 27, 2018
Extensible Binary Meta Language Extensible Binary Meta Language
draft-ietf-cellar-ebml-07 draft-ietf-cellar-ebml-08
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 29, 2019. This Internet-Draft will expire on May 31, 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 36, line 19 skipping to change at page 36, line 19
path: "0*(\EBML\DocTypeExtension)" path: "0*(\EBML\DocTypeExtension)"
id "0x4281" id "0x4281"
minOccurs: 0 minOccurs: 0
type: "Master Element" type: "Master Element"
description: A "DocTypeExtension" adds extra "Elements" to the main description: A "DocTypeExtension" adds extra "Elements" to the main
"DocType"+"DocTypeVersion" tuple it's attached to. An "EBML Reader" "DocType"+"DocTypeVersion" tuple it's attached to. An "EBML Reader"
MAY understand these extra "Elements". A "DocTypeExtension" MAY be MAY know these extra "Elements" and how to use them. A
used to iterate between experimental "Elements" before they are "DocTypeExtension" MAY be used to iterate between experimental
integrated in a regular "DocTypeVersion". Reading one "Elements" before they are integrated in a regular "DocTypeVersion".
"DocTypeExtension" version of a "DocType"+"DocTypeVersion" tuple Reading one "DocTypeExtension" version of a
doesn't imply one should be able to read upper values of this "DocType"+"DocTypeVersion" tuple doesn't imply one should be able to
"DocTypeExtension". read upper values of this "DocTypeExtension".
13.2.10. DocTypeExtensionName Element 13.2.10. DocTypeExtensionName Element
name: "DocTypeExtensionName" name: "DocTypeExtensionName"
path: "1*1(\EBML\DocTypeExtension\Name)" path: "1*1(\EBML\DocTypeExtension\Name)"
id "0x4283" id "0x4283"
minOccurs: 1 minOccurs: 1
maxOccurs: 1 maxOccurs: 1
size: >0 size: >0
type: String type: String
description: The name of the "DocTypeExtension" to identify it from description: The name of the "DocTypeExtension" to identify it from
other "DocTypeExtension" of the same "DocType"+"DocTypeVersion" other "DocTypeExtension" of the same "DocType"+"DocTypeVersion"
tuple. tuple. A "DocTypeExtensionName" value MUST be unique within the
"EBML Header".
13.2.11. DocTypeExtensionVersion Element 13.2.11. DocTypeExtensionVersion Element
name: "DocTypeExtensionVersion" name: "DocTypeExtensionVersion"
path: "1*1(\EBML\DocTypeExtension\Version)" path: "1*1(\EBML\DocTypeExtension\Version)"
id "0x4284" id "0x4284"
minOccurs: 1 minOccurs: 1
maxOccurs: 1 maxOccurs: 1
range: not 0 range: not 0
type: Unsigned Integer type: Unsigned Integer
description: The version of the "DocTypeExtension". Different description: The version of the "DocTypeExtension". Different
"DocTypeExtensionVersion" values of the same "DocTypeExtensionVersion" values of the same
skipping to change at page 41, line 5 skipping to change at page 41, line 8
Registry". Registry".
DocType values are described in Section 13.1.2.1. DocTypes are ASCII 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 strings, defined in Section 8.4, which label the official name of the
"EBML Document Type". The strings may be allocated according to "EBML Document Type". The strings may be allocated according to
First Come First Served (see [RFC8126]). First Come First Served (see [RFC8126]).
The use of ASCII corresponds to the types and code already in use, The use of ASCII corresponds to the types and code already in use,
the value is not meant to be visible to the user. the value is not meant to be visible to the user.
DocType string values of "matroska" and "webm" are reserved for pre- DocType string values of "matroska" and "webm" are reserved to the
existing formats. IETF for future use. These can be assigned via IESG Approval or RFC
Required.
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.
 End of changes. 9 change blocks. 
14 lines changed or deleted 16 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/