[Cellar] Éric Vyncke's Discuss on draft-ietf-cellar-codec-19: (with DISCUSS and COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 27 July 2026 10: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 133D311F2EEFB; Mon, 27 Jul 2026 03:42:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785148931; bh=oO2IzTekx7SP4Ki8Rvhx6D3TjbRHiNo/UHfyPgMw5fQ=; h=From:To:Cc:Subject:Reply-To:Date; b=bUmLS8GxPUCUVOsthgYMYT8kUoSQxyXjvEsTnERR+S8ypTQ+6s4ejtAuA66u78Tok dKJsVg2CDbI4fXOhE2XXVeT0j1UD4hPrPkftX1buTjwqzuNd5Uwv9xHVSRlvy4DRyI 9pL3Ke/SN6xmQ1o6c94KddrFNfMx6Lc+KQXVCXRI=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke 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: <178514893082.1174668.1139535686505885700@dt-datatracker-d4d6ff9d9-fsx7d>
Date: Mon, 27 Jul 2026 03:42:10 -0700
Message-ID-Hash: 32THJV6S7Z65K4VGKY5Q2ZOTWCFXAN2G
X-Message-ID-Hash: 32THJV6S7Z65K4VGKY5Q2ZOTWCFXAN2G
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: Éric Vyncke <evyncke@cisco.com>
Subject: [Cellar] Éric Vyncke'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/n9oiAOyfp4eDfkM1Y_3xLA6lDOE>
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>

Éric Vyncke 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:
----------------------------------------------------------------------

Thanks for the work done in this document.

I am balloting a blocking DISCUSS, but it should be trivial to address by
adding a normative reference to `Xiph-style` in section 3.3.25.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Except for one `SHOULD` that follows the IESG statement on BCP14:
https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/,
I wonder why the remaining `SHOULD` are not "MUST" ? Please also the IESG
statement by providing guidance about the consequences (even if obvious to the
authors) of not following the `SHOULD`.