IETF Logo Mail Archive

[AVTCORE] Re: Errata on RFC 8888 - number of reports

Harald Alvestrand <harald@alvestrand.no> Thu, 19 December 2024 10:49 UTC

Return-Path: <harald@alvestrand.no>
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 78B43C151553 for <avt@ietfa.amsl.com>; Thu, 19 Dec 2024 02:49:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 lhdux9MuYs3t for <avt@ietfa.amsl.com>; Thu, 19 Dec 2024 02:49:21 -0800 (PST)
Received: from smtp.alvestrand.no (smtp.alvestrand.no [65.21.189.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86688C151522 for <avt@ietf.org>; Thu, 19 Dec 2024 02:49:20 -0800 (PST)
Received: from [192.168.3.231] (unknown [82.148.179.49]) by smtp.alvestrand.no (Postfix) with ESMTPSA id 6A02B4EEDC; Thu, 19 Dec 2024 11:49:19 +0100 (CET)
Message-ID: <b62ed96c-1937-4cf3-a951-0eb2e9b1f189@alvestrand.no>
Date: Thu, 19 Dec 2024 11:49:18 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: avt@ietf.org, Colin Perkins <csp@csperkins.org>
References: <1c6a3b7b-a292-46cd-8baf-77828022abaf@alvestrand.no>
Content-Language: en-US
From: Harald Alvestrand <harald@alvestrand.no>
Autocrypt: addr=harald@alvestrand.no; keydata= xjMEZ0mTQBYJKwYBBAHaRw8BAQdAggX3PGSWWM78d4EKr8BjFdZhh4Vk73S5/eW3LW8Zpg3N KEhhcmFsZCBBbHZlc3RyYW5kIDxoYXJhbGRAYWx2ZXN0cmFuZC5ubz7CjwQTFggANxYhBKML Oen7rVm4eJicvjofELrAkOUSBQJnSZNABQkFo5qAAhsDBAsJCAcFFQgJCgsFFgIDAQAACgkQ Oh8QusCQ5RLllgEAwXOwOahi4l5QZ56KEAiSE5NatgPtzG4/YLTFDQL7VnsA/jLF3aqVpJuT Rx1I6XL7pl0rqPgA3YFkmhvxJicnT+wMzjgEZ0mTQBIKKwYBBAGXVQEFAQEHQC/TfFw6aX0M /CoUaD3Um5QWJ6Io2sfhxqvylJjEipFmAwEIB8J+BBgWCAAmFiEEows56futWbh4mJy+Oh8Q usCQ5RIFAmdJk0AFCQWjmoACGwwACgkQOh8QusCQ5RJe2AD8CdqXoVNNiPHtx+KvfsyRZriN v5U5kNC9Bwzeb1TQ/cwA/0e2MkUpxn1bCVMYfZ7mMyVb14YWJRxY445SVphDBdwP
In-Reply-To: <1c6a3b7b-a292-46cd-8baf-77828022abaf@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: PVQR35D2W5UEIT2PPYVAWYT5K7XZ4KVK
X-Message-ID-Hash: PVQR35D2W5UEIT2PPYVAWYT5K7XZ4KVK
X-MailFrom: harald@alvestrand.no
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [AVTCORE] Re: Errata on RFC 8888 - number of reports
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/FeGOxeOIO3rUwUgKyUzrV6PxbEA>
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>

I'm missing any response to this errata - it's kind of important since 
we're in the middle of coding this support, and we have verified that 
the disagreement over what it should say has led to interop issues.

Anyone?

Harald


On 11/19/24 13:29, Harald Alvestrand wrote:
> This was discovered during interop testing at IETF 121, but hasn't hit 
> the list yet as far as I can see.
> 
> Report:
> 
> https://www.rfc-editor.org/errata/eid8166
> 
> Basically, there are two ways to interpret how many packets to report on 
> in a feedback message, and Netflix and Chrome had chosen incompatible 
> interpreations.
> 
> Can we settle this one way or the other?
> 
> Harald
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> To unsubscribe send an email to avt-leave@ietf.org

v2.29.0 | Report a Bug | By Email | System Status