[AVTCORE] [IANA #1287105] [Errata Verified] RFC9134 (6752)
Amanda Baber via RT <iana-matrix@iana.org> Sat, 25 November 2023 03:27 UTC
Return-Path: <iana-shared@icann.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D52A2C151993 for <avt@ietfa.amsl.com>; Fri, 24 Nov 2023 19:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.957
X-Spam-Level:
X-Spam-Status: No, score=-3.957 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R23olH6DOwFU for <avt@ietfa.amsl.com>; Fri, 24 Nov 2023 19:27:39 -0800 (PST)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8342C151992 for <avt@ietf.org>; Fri, 24 Nov 2023 19:27:39 -0800 (PST)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 0D6CFE13CC; Sat, 25 Nov 2023 03:27:39 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id 0B09252F36; Sat, 25 Nov 2023 03:27:39 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-matrix@iana.org>
Reply-To: iana-matrix@iana.org
In-Reply-To: <20231108084212.BD1E2AE80@rfcpa.amsl.com>
References: <RT-Ticket-1287105@icann.org> <20231108084212.BD1E2AE80@rfcpa.amsl.com>
Message-ID: <rt-5.0.3-105373-1700882858-795.1287105-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1287105
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
To: rfc-editor@rfc-editor.org
CC: superuser@gmail.com, thomas.richter@iis.fraunhofer.de, t.bruylants@intopix.com, c.damman@intopix.com, avt@ietf.org, antonin.descampe@uclouvain.be
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Sat, 25 Nov 2023 03:27:39 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/ju6fnFoX4wEZqd0regpSaNtZlT0>
Subject: [AVTCORE] [IANA #1287105] [Errata Verified] RFC9134 (6752)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 25 Nov 2023 03:27:43 -0000
Hi, Should this errata report be listed as an additional reference for video/jxsv? See https://www.iana.org/assignments/media-types https://www.iana.org/assignments/rtp-parameters thanks, Amanda Baber IANA Operations Manager On Wed Nov 08 08:42:33 2023, rfc-editor@rfc-editor.org wrote: > The following errata report has been verified for RFC9134, > "RTP Payload Format for ISO/IEC 21122 (JPEG XS)". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid6752 > > -------------------------------------- > Status: Verified > Type: Technical > > Reported by: Tim Bruylants <t.bruylants@intopix.com> > Date Reported: 2021-11-24 > Verified by: Murray Kucherawy (IESG) > > Section: 4.2 > > Original Text > ------------- > As specified in [RFC3550] and [RFC4175], the RTP timestamp > designates the sampling instant of the first octet of the video > frame to which the RTP packet belongs. Packets SHALL NOT include > data from multiple video frames, and all packets belonging to the > same video frame SHALL have the same timestamp. Several > successive RTP packets will consequently have equal timestamps if > they belong to the same video frame (that is until the marker bit > is set to 1, marking the last packet of the video frame), and the > timestamp is only increased when a new video frame begins. > > Corrected Text > -------------- > As specified in [RFC3550] and [RFC4175], the RTP timestamp > designates the sampling instant of the first octet of the video > frame/field to which the RTP packet belongs. Packets SHALL NOT > include > data from multiple video frames/fields, and all packets belonging to > the > same video frame/field SHALL have the same timestamp. Several > successive RTP packets will consequently have equal timestamps if > they belong to the same video frame/field (that is until the marker > bit > is set to 1, marking the last packet of the video frame/field), and > the > timestamp is only increased when a new video frame/field begins. > > Notes > ----- > This RFC follows RFC4175 (and also SMPTE2110) for timestamping RTP > packets. The intent has always been to have unique timestamps per > progressive video frame and/or per interlaced video field (two fields > of a frame MUST be allowed to have different timestamps). This is > correctly reflected by the marker bit (M) that is used to indicate the > last packet of a frame/field (which is correctly explained in this > RFC). However, the accompanied text about the timestamp in section 4.2 > does not properly formulate this for the interlaced mode case (it was > an editorial oversight), which can cause confusion to implementers of > this RFC. > > -------------------------------------- > RFC9134 (draft-ietf-payload-rtp-jpegxs-18) > -------------------------------------- > Title : RTP Payload Format for ISO/IEC 21122 (JPEG XS) > Publication Date : October 2021 > Author(s) : T. Bruylants, A. Descampe, C. Damman, T. Richter > Category : PROPOSED STANDARD > Source : Audio/Video Transport Core Maintenance > Area : Applications and Real-Time > Stream : IETF > Verifying Party : IESG
- [AVTCORE] [Errata Verified] RFC9134 (6752) RFC Errata System
- [AVTCORE] [IANA #1287105] [Errata Verified] RFC91… Amanda Baber via RT
- Re: [AVTCORE] [IANA #1287105] [Errata Verified] R… Tim Bruylants