Skip to content

Commit

Permalink
Remove tags Status Of This Document section
Browse files Browse the repository at this point in the history 
The IETF status doesn't matter. The document is found at the IETF anyway.
We already describe the goal of the document in the Introdution.

And the EBML RFC doesn't has a status either. The Matroska document has one
because it deals with versions of Matroska.
  • Loading branch information
@robUx4
robUx4 committed Oct 15, 2023
1 parent 085e13e commit 20a8f7f
Showing 1 changed file with 0 additions and 6 deletions.
6 changes: 0 additions & 6 deletions index_tags.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -51,12 +51,6 @@ in a `Matroska Segment`. It can tag a whole `Segment`, separate `Track Elements`
While the Matroska tagging framework allows anyone to create their own custom tags, it's important to have a common
set of values for interoperability. This document intends to define a set of common tag names used in Matroska.

# Status of this document

This document is a work-in-progress specification defining the Matroska file format as part
of the [IETF Cellar working group](https://datatracker.ietf.org/wg/cellar/charter/).
It uses basic elements and concept already defined in the Matroska specifications defined by this workgroup [@!Matroska].

# Notation and Conventions

The key words "**MUST**", "**MUST NOT**",
Expand Down

0 comments on commit 20a8f7f

Please sign in to comment.