[AVTCORE] Benjamin Kaduk's No Objection on draft-ietf-payload-rtp-jpegxs-16: (with COMMENT)
Benjamin Kaduk via Datatracker <noreply@ietf.org> Thu, 17 June 2021 07:45 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2F5C3A1161; Thu, 17 Jun 2021 00:45:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-payload-rtp-jpegxs@ietf.org, avtcore-chairs@ietf.org, avt@ietf.org, Ali Begen <ali.begen@networked.media>, bernard.aboba@gmail.com, bernard.aboba@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.32.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <162391594041.10475.10269870855508874539@ietfa.amsl.com>
Date: Thu, 17 Jun 2021 00:45:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/jbrQsVvE7ctwyllROEYy8J45jCw>
Subject: [AVTCORE] Benjamin Kaduk's No Objection on draft-ietf-payload-rtp-jpegxs-16: (with COMMENT)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2021 07:45:41 -0000
Benjamin Kaduk has entered the following ballot position for draft-ietf-payload-rtp-jpegxs-16: 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/iesg/statement/discuss-criteria.html for more information about DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-jpegxs/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I'll echo the sentiment of other reviewers that the scope of review possible is limited witout access to the underlying ISO specification. I further note that in the recent case of https://datatracker.ietf.org/doc/draft-ietf-payload-vp9/ (for which the underlying specification is freely available), there was an error in replicating the chroma subsampling details from the underlying reference to the internet-draft. Any such errors are undetectable for this draft. Section 4.3 Does the value of the T and K bits need to be identical for all packets of a given RTP stream? Section 4.4 It's perhaps needlessly confusing to have the human-readable slice labels in Figures 8 and 9 start at 1 but the SEP counter start at 0. nit: if SLH is an acronym it should be expanded somewhere (it only appears in the figures, at present). In the slice packetization modes, do we have reasonable guarantees that the JPEG XS header (including all markers and marker segments) will fit into a single RTP packet? Section 7.1 Applications that use this media type: For example: SMPTE ST 2110, Video over IP, Video conferencing, Broadcast applications. I think bland declarative statements like "applications that transmit video over RTP" tend to be more common than longer "for example" listings, in this type of registration. Section 8 nit: s/SPD/SDP in the section heading.
- [AVTCORE] Benjamin Kaduk's No Objection on draft-… Benjamin Kaduk via Datatracker
- Re: [AVTCORE] Benjamin Kaduk's No Objection on dr… Tim Bruylants
- Re: [AVTCORE] Benjamin Kaduk's No Objection on dr… Benjamin Kaduk