[Cellar] Re: Gorry Fairhurst's Discuss on draft-ietf-cellar-tags-20: (with DISCUSS and COMMENT)

Steve Lhomme <slhomme@matroska.org> Sun, 11 January 2026 09:20 UTC

Return-Path: <slhomme@matroska.org>
X-Original-To: cellar@mail2.ietf.org
Delivered-To: cellar@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 49FD5A604E8B for <cellar@mail2.ietf.org>; Sun, 11 Jan 2026 01:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=matroska-org.20230601.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gua49TfLItJw for <cellar@mail2.ietf.org>; Sun, 11 Jan 2026 01:20:53 -0800 (PST)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 85726A604E69 for <cellar@ietf.org>; Sun, 11 Jan 2026 01:20:53 -0800 (PST)
Received: by mail-wm1-x32c.google.com with SMTP id 5b1f17b1804b1-47798f4059fso5405385e9.2 for <cellar@ietf.org>; Sun, 11 Jan 2026 01:20:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=matroska-org.20230601.gappssmtp.com; s=20230601; t=1768123247; x=1768728047; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=g66iP9TZvaOwPX9mBs+jv6hZO+H0fEVf0E86jnj7pQU=; b=ytWV0tiTfCWIRr6M1puFb7qfBZUsGCFMa/1+r5yQpCD0mczjlf9s5f3ou485+DF8Sc R/l0Wv17MT3tW5t9UtZ8Ic/8iMoMf+fyElTGgyhylN0b81+qINs17eNAPu9JospKpJbW 3tuCG2fD4hZ1RU9mj0kEFxJLmA8u2SfA8TugpPs+6f06jUJfWn/Qsc/sjg+X8CQn/c0t xX6uDwOWFCmed0f1uJ3d4AeP9ibPmFIAoUNOZz0DIGJOlfzMn79DqsXOGxbQKvZSsAmf Vuilk5nc5Z+jQpc11LKbp1yr1a6REWwsCjGVcduRWlQ/ENMM+nEvoAY9BRBJRkLq+vDs Ml4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768123247; x=1768728047; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=g66iP9TZvaOwPX9mBs+jv6hZO+H0fEVf0E86jnj7pQU=; b=dS9hMMeqAhhcQQJ+2iOwEUzk9gTxbR2XJVjV8IueXWvZM1TFZUxhMJ2r0O4SEFlZJJ MpsQD73HQfIDthR4b8c7kbX65mUuJEuhSvnrim0kTNoMXyagMtTu1kuujje8cCYNC3ou 1iI2Rm5c6/ANrtPB5nY2ZeU+esIawz+q9esmWzjIQlYbC2zCjFt8PS6+0CRr3lAclwTg KPdFNm6W0MNi3OIsN7ERW0JjGw8Jch9heyh3wuzWbIG1UAzk+eUFaOTGNGEsLRFP+WIG OqQkoTTlg6ugAAa2Ym1UWbxu/gzzcFW8u6VZ7eUgXifi2IFYrwr7+bNc7cm6HfIxvrXG CEnQ==
X-Forwarded-Encrypted: i=1; AJvYcCXA+Ae5P4Nd1/UibP5Bv2aoyZDRALAMVMEv/egXuGDvGwDR11l9JPefyLwUzKTybIH/YFyWR9E=@ietf.org
X-Gm-Message-State: AOJu0YxEUNjKi57kIBWPolGliMalCn2Q07Rs0/kCdTDpUjuV0nu2Qakz JhlzAx+XTE7YuWiq53e7Jxa39nB/V6S0KFU427Fd+UyQsBsqBnuLZTGnB7W2CwhKxQ==
X-Gm-Gg: AY/fxX5BmGPLL0kFNi99jsqKK4oeMnk6FA+3bwx+6t60tY0/Ls6oCs4uDlHHft4muhq SrpZup+P4I9WrTj4PNQT6Qs9ybltA0XOOfNhyqo24OIzByDstlIRAOyoWf6d9fj3W3iDbtnXMOD zD5n+rLURmgql96lDeif0ZJlM6qm2GeGsD5sF3/dXOLvsMRhJArRCGGiU3nK0avN85IyL28FQVH RPOFuTVo3GiaJkD4UhwA2ceerZAblV1P7x9dGM4S3BvKPAb1+R45n+wuUwzW2iiBwOexU+/pua8 Kl0Nb6x8HKOMgCTYtv9TiPywmjE1yt5Qxe8iUQMB2R27x45ZENdAPr4RBJpWg5z7R2E2kzj1YNT 3XaRhLd8ufgxDae8jkK3D+bFIYIgRp5v7EFa73lDMMgMZV/2tUIXOb/1JXgr9DsqXRCgcy67xI4 QDhSNPqSJiPiM52xgu+OJkT8/DZzOAFvR+UuQ=
X-Google-Smtp-Source: AGHT+IEMxYbdFT+JcU0qLnXl3CmWMnNuNn/KoDYPj/1/f3rqHXfRmgB3JZacAxrNp2Ye2Pzfu5sT1Q==
X-Received: by 2002:a05:600c:c173:b0:477:9fa8:bc99 with SMTP id 5b1f17b1804b1-47d84b34c56mr94868245e9.4.1768123245925; Sun, 11 Jan 2026 01:20:45 -0800 (PST)
Received: from smtpclient.apple ([2001:861:34c4:290:e07a:3c32:ea2c:ac3]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-432dd78f5a8sm12102535f8f.27.2026.01.11.01.20.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 11 Jan 2026 01:20:45 -0800 (PST)
From: Steve Lhomme <slhomme@matroska.org>
Message-Id: <4B45B6D8-7B55-4EB5-9070-951D42C3381E@matroska.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_21F2A8FA-C3DC-44F7-A7A6-DA8B0004AB9F"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81.1.3\))
Date: Sun, 11 Jan 2026 10:20:35 +0100
In-Reply-To: <176607465608.1062366.11961779923430145710@dt-datatracker-5bd94c585b-pvtsm>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
References: <176607465608.1062366.11961779923430145710@dt-datatracker-5bd94c585b-pvtsm>
X-Mailer: Apple Mail (2.3826.700.81.1.3)
Message-ID-Hash: FDDC5ISAB4QGUBPZCSPCKLZ7FPN474LF
X-Message-ID-Hash: FDDC5ISAB4QGUBPZCSPCKLZ7FPN474LF
X-MailFrom: slhomme@matroska.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cellar.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, cellar-chairs@ietf.org, cellar@ietf.org, draft-ietf-cellar-tags@ietf.org, spencerdawkins.ietf@gmail.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Cellar] Re: Gorry Fairhurst's Discuss on draft-ietf-cellar-tags-20: (with DISCUSS and COMMENT)
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/e3i4QoCNzZ6X96h_ObyNIafkc98>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Owner: <mailto:cellar-owner@ietf.org>
List-Post: <mailto:cellar@ietf.org>
List-Subscribe: <mailto:cellar-join@ietf.org>
List-Unsubscribe: <mailto:cellar-leave@ietf.org>

Hi Gorry,

Thanks for a review. My comments below:

> On 18 Dec 2025, at 17:17, Gorry Fairhurst via Datatracker <noreply@ietf.org> wrote:
> 
> Gorry Fairhurst has entered the following ballot position for
> draft-ietf-cellar-tags-20: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-cellar-tags/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> I have two document concerns: Relating to current text that says: "Matroska Tag
> Names for binary data are to be allocated according to the "Specification
> Required" policy [RFC8126]."
> 
> * I support the DISCUSS by Med, relating to the need for additional text in the
> IANA Section on the Specification required policy, and guidance for Designated
> Experts (DE).

OK, now I understand what DE stands for.

This should be handled the same way as we have some Matroska IDs that have a "Specification Required” policy: https://www.rfc-editor.org/rfc/rfc9559#name-matroska-element-ids-regist
One-octet and two-octet Matroska Element IDs.

The experts have been assigned for these (Dave and myself): https://www.iana.org/assignments/matroska/matroska.xhtml#matroska-element-ids 

> * I'd like to DISCUSS the use the word "Official" in this I-D, because I find
> this is an unusual word to use in an IETF Specification to describe an entry in
> an IANA Registry. I'd expect to see a word such as "assigned" or "allocated".

This is the terminology we have used in the documentation for 20+ years and that was carried over to this document.
I replaced Official with Assigned as you suggested and it does work better IMO: https://github.com/ietf-wg-cellar/matroska-specification/pull/1048

We may not even need to specify that “assigned” elements are the one in the IANA registry in https://github.com/ietf-wg-cellar/matroska-specification/pull/1047 since that’s the terminology used in the IANA regsitry.

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I have several comments that I hope may improve this:
> 
> 1. Please could you make this abstract more descriptive? It's hard to
> understand what the document might contain from the abstract. There are many
> sentences in the introduction that would help. For example these text fragments
> could be helpful;:
> 
> Matroska is a multimedia container format that can store timestamped multimedia
> data but also chapters and tags. ... This document defines  ... a set of common
> tag names used in Matroska. These Tag elements add metadata to identify and
> classify the information found in a Matroska Segment. ...

I reordered the text so that it starts with something more general in https://github.com/ietf-wg-cellar/matroska-specification/pull/1050 

> 2. The document contains the names of several example physical entities in the
> entertainment industry. I am not yet persuaded that this necessary or even
> helpful to have actual rather than exemplar identities named.

This issue is addressed by https://github.com/ietf-wg-cellar/matroska-specification/pull/1045 

> 3. There is a section on Official Tags, which says: "The following is a
> complete list of the supported Matroska Tags." -- Is that the present value?
> The only permitted value until this RFC-to-be is updated? This is often phrased
> as /complete/assigned/ or some similar change (see DISCUSS point).

This is indeed not the complete and final list of tags but the initial list. This is addressed in https://github.com/ietf-wg-cellar/matroska-specification/pull/1049 

Thanks again for your review.