[AVTCORE] Charles Eckel's No Objection on draft-ietf-avtcore-rtp-jpegxs-3ed-03: (with COMMENT)

Charles Eckel via Datatracker <noreply@ietf.org> Tue, 07 July 2026 22:13 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@mail2.ietf.org
Received: from [10.244.21.96] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 00EC8112795E9; Tue, 7 Jul 2026 15:13:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783462401; bh=FogZNJmKF8s0O9v63EIe9R7kVKntAIpzckztsX2C00o=; h=From:To:Cc:Subject:Reply-To:Date; b=YrfWsaFDO6wTVKHA2n+frhdlkjyquvGc6PYZZ1p4+NAF4WzYGxeiKa59mQ/n4ZitD ltT+k/M15IRplpsRmlLb0NUqfRpwwA/85jDa+naJj0HHBa0FTiK3m2RJWAuQlymtlG xUvkZSTzhOfka8B+2vQSbbKUs27PxNDtfyMQP94s=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Charles Eckel via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.68.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178346240072.516669.4115418351592303563@dt-datatracker-57b5d8f849-v5cht>
Date: Tue, 07 Jul 2026 15:13:20 -0700
Message-ID-Hash: 6JEZVWJKTTTW4ACN7O5CF2JTOVFONQWP
X-Message-ID-Hash: 6JEZVWJKTTTW4ACN7O5CF2JTOVFONQWP
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-avt.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: avt@ietf.org, avtcore-chairs@ietf.org, draft-ietf-avtcore-rtp-jpegxs-3ed@ietf.org, ietf@mariuskleidl.net
X-Mailman-Version: 3.3.9rc6
Reply-To: Charles Eckel <eckelcu@cisco.com>
Subject: [AVTCORE] Charles Eckel's No Objection on draft-ietf-avtcore-rtp-jpegxs-3ed-03: (with COMMENT)
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/Hkr6fcPqzO-n048ad17vlFCYTsg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Owner: <mailto:avt-owner@ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Subscribe: <mailto:avt-join@ietf.org>
List-Unsubscribe: <mailto:avt-leave@ietf.org>

Charles Eckel has entered the following ballot position for
draft-ietf-avtcore-rtp-jpegxs-3ed-03: No Objection

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-avtcore-rtp-jpegxs-3ed/



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

# Charles Eckel, ART AD, comments for draft-ietf-avtcore-rtp-jpegxs-3ed-03
CC @eckelcu

* line numbers:
  -
  https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-jpegxs-3ed-03.txt&submitcheck=True

* comment syntax:
  - https://github.com/mnot/ietf-comments/blob/main/format.md

* "Handling Ballot Positions":
  - https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/

## Comments

### Default value for fbblevel

The fbblevel parameter is listed as optional, but the text does not explicitly
state the default behavior or value if the parameter is omitted in an SDP offer.

985        Optional parameters:
:
1007          fbblevel:  The JPEG XS frame buffer level [ISO21122-2] in use.

1009             Any white space Unicode character in the fbblevel name SHALL be
1010             omitted.  Examples of valid frame buffer levels are
1011             'Fbblev3bpp' or 'Fbblev12bpp'.

Would it be helpful to add a sentence to the fbblevel description such as, "If
the parameter is not specified, it SHALL be assumed that the TDC coding mode is
not used, or that the frame buffer level is zero."

I ask this in reference to the newly added fbblevel parameter, but I see there
are other optional parameters for which no default behavior or value is
specified.