Skip to main content

Extensible Binary Meta Language
RFC 8794

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: The IESG <>,,,, Steven Villereal <>,,,
Subject: Protocol Action: 'Extensible Binary Meta Language' to Proposed Standard (draft-ietf-cellar-ebml-17.txt)

The IESG has approved the following document:
- 'Extensible Binary Meta Language'
  (draft-ietf-cellar-ebml-17.txt) as Proposed Standard

This document is the product of the Codec Encoding for LossLess Archiving and
Realtime transmission Working Group.

The IESG contact persons are Adam Roach, Alexey Melnikov and Barry Leiba.

A URL of this Internet Draft is:

Ballot Text

Technical Summary

   This document defines format considerations for Extensible Binary
   Meta Language, a hierarchical file format for efficient delivery
   of binary data in defined Elements inspired by XML. It proposes
   definitions for creating and validating EBML Schemas that define
   the use and interpretation of Elements within EBML Documents.  

Working Group Summary

   This document has been adequately reviewed by working group
   members and others, through both mailing list discussion and
   Github issues and pull requests.

   One minor issue was how to define EBML Elements in a Header
   document in a forward-compatible way. It was decided Headers
   could require a specific, minimum or maximum EBMLVersion
   (which might have different implementations of Elements). 

   Most recent discussion has focused on how Element IDs (unique
   identifiers for EBML Elements used within a Schema and Document)
   should be defined and encoded (as Variable Size Integers) with regard
   to IANA registration.

Document Quality

   There are already several existing implementations of the specification,
   including ffmpeg, vlc, and most major browsers and many TV boxes.

   This is a very readable and clearly written document, and represents
   the inclusion of multiple recent revisions resolving minor outstanding issues.
   There appears to be strong group consensus on this document’s readiness
   to move forward in the standardization process.


   The document shepherd is Steven Villereal.
   The responsible Area Director is Alexey Melnikov.

RFC Editor Note