[Cellar] Roman Danyliw's Discuss on draft-ietf-cellar-codec-19: (with DISCUSS and COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Fri, 31 July 2026 20:42 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: cellar@ietf.org
Delivered-To: cellar@mail2.ietf.org
Received: from [10.244.21.25] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id E2492121DC3FE; Fri, 31 Jul 2026 13:42:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785530523; bh=9dtkmbM8YHQgdwyQX0NUj8fqZcSFaXiZa31wWcCej8I=; h=From:To:Cc:Subject:Reply-To:Date; b=MhYDMBGmTB/p0w2ZrW1XpQ2BnHZBsd7PfUhaIVvrhDyaHurjv/B5fcwSbTsa0LfYL aIKPKIckbvWcBfVJFxisuK/ydm9HW7MJ494NH55u+GCHjeAUDP4HbckBZEEYyGJqo/ nQbDSdDx99h8191PeltWRemSjqUhcGkkXkENPBek=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178553052267.1548497.4766707787835124626@dt-datatracker-d4d6ff9d9-fsx7d>
Date: Fri, 31 Jul 2026 13:42:02 -0700
Message-ID-Hash: 7YINGK34PJV3NJQ2K2NFG44K3RAPYOU2
X-Message-ID-Hash: 7YINGK34PJV3NJQ2K2NFG44K3RAPYOU2
X-MailFrom: noreply@ietf.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: cellar-chairs@ietf.org, cellar@ietf.org, draft-ietf-cellar-codec@ietf.org, spencerdawkins.ietf@gmail.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Roman Danyliw <rdd@cert.org>
Subject: [Cellar] Roman Danyliw's Discuss on draft-ietf-cellar-codec-19: (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/A1jvIUFa9WmpUPsDIZFi8VOgyYY>
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>
Roman Danyliw has entered the following ballot position for draft-ietf-cellar-codec-19: 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-codec/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- ** Sections 3.1.6 and 8.1 -- Section 3.1.6, “Citation, Documentation of the associated normative and informative references for the codec is RECOMMENDED.” -- Section 8.1, “To register a new Codec ID in this registry, one needs a Codec ID string, … and an optional Reference to a document describing the Codec ID”. How is interoperability ensured if the code point for a given Codec ID has no associated reference for the implementer to use? Should the registration policy be “Specification Required”? ** For the responsible AD/WG Chairs – could the consensus to publish this document please be checked (and as appropriate, documented). What I found in the record was: 26-August-2026 – Interim meeting, https://datatracker.ietf.org/doc/minutes-interim-2025-cellar-08-202508261900/, one WG participant on the call who wasn’t the WG chair or a document author. No call for consensus on the call 26-August-2026 – WGLC Started on the Mailing List, https://mailarchive.ietf.org/arch/msg/cellar/gDR-EVk6j-IABAJGceMLv7qX47Q/. There were no responses to this WGLC. 23-September-2026 – Interim meeting, https://datatracker.ietf.org/doc/minutes-interim-2025-cellar-09-202509231900/, following the WGLC with the same situation as the 26-August meeting (one WG participant who wasn’t the WG chair or a document author. No documented instance of trying to establish consensus) 14-October-2026 – WGLC closed, consensus called, https://mailarchive.ietf.org/arch/msg/cellar/wyKO4yLu4ZuSidsmq2LF7wESYak/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Mallory Knodel for the GENART review. I support the DISCUSS positions of Éric Vyncke and Ketan Talaulikar. ** Section 3. What is the expected behavior of an implementation when encountering a CodecID that is not registered? ** Section 3.5.13. The reference for VobSub files appears to be to [VobSub] MultimediaWiki, "VOBSub", 21 March 2007, <https://wiki.multimedia.cx/index.php?title=VOBsub>. However, that page provides an example, not a specification for the format. This wiki page references a SourceForge project, https://sourceforge.net/projects/guliverkli/files/? Is that the reference? Where in the code repository is the format? Is there a better reference? ** Sections 4.1.1.1, 4.1.1.2, 4.1.2.2. These sections appear to use a formal notation. Please cite the format. Perhaps the reference should be to C99? ** Sections 5. This entire section appears to be verbatim (cut-and-paste) from https://www.matroska.org/technical/subtitles.html. I don’t know the pedigree of the text but consider if some kind of acknowledgement of citation is needed in this document. ** Section 5.1. I was unable to access this site (or even resolve the DNS name): DVD Forum, "DVD-Books: Part 3 DVD-Video Book", November 1995, <http://www.dvdforum.org/>. ** Section 5.3. Editorial. Consider revising the colloquial framing of the text following “Now, how are they stored in Matroska?” to be more consistent with the rest of the text.
- [Cellar] Roman Danyliw's Discuss on draft-ietf-ce… Roman Danyliw via Datatracker