[AVTCORE] [Errata Verified] RFC8888 (7894)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 21 May 2024 13:44 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown []) (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 44738C14F6A3; Tue, 21 May 2024 06:44:42 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 807431DEB87; Tue, 21 May 2024 06:44:41 -0700 (PDT)
To: harald@alvestrand.no, Zaheduzzaman.Sarker@ericsson.com, csp@csperkins.org, varun.singh@iki.fi, mar42@cornell.edu
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240521134441.807431DEB87@rfcpa.rfc-editor.org>
Date: Tue, 21 May 2024 06:44:41 -0700
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Hits: max-recipients
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-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Approved-At: Tue, 21 May 2024 09:00:58 -0700
CC: zaheduzzaman.sarker@nokia.com, iesg@ietf.org, avt@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [AVTCORE] [Errata Verified] RFC8888 (7894)
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/u1CntmRqzB9oinw4AxICnNnZZ7U>
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>

The following errata report has been verified for RFC8888,
"RTP Control Protocol (RTCP) Feedback for Congestion Control". 

You may review the report below and at:

Status: Verified
Type: Technical

Reported by: Harald Tveit Alvestrand <harald@alvestrand.no>
Date Reported: 2024-04-16
Verified by: Zaheduzzaman Sarker (IESG)

Section: 3.1

Original Text
   RTCP Congestion Control Feedback Packets SHOULD include a report
   block for every active SSRC.

Corrected Text
   RTCP Congestion Control Feedback Packets SHOULD include a report
   block for every SSRC where packets have been received since the
   previous report was generated.

The term "active" is ambiguous. Discussion on the avtcore mailing list indicates that this is the intended meaning.

RFC8888 (draft-ietf-avtcore-cc-feedback-message-09)
Title               : RTP Control Protocol (RTCP) Feedback for Congestion Control
Publication Date    : January 2021
Author(s)           : Z. Sarker, C. Perkins, V. Singh, M. Ramalho
Category            : PROPOSED STANDARD
Source              : Audio/Video Transport Core Maintenance
Stream              : IETF
Verifying Party     : IESG