Re: [AVTCORE] RFC 8888 clarification: What does "active" mean?

Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com> Thu, 11 April 2024 09:37 UTC

Return-Path: <zahed.sarker.ietf@gmail.com>
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 4F3BBC14F681 for <avt@ietfa.amsl.com>; Thu, 11 Apr 2024 02:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HvJDgDFzuNef for <avt@ietfa.amsl.com>; Thu, 11 Apr 2024 02:36:56 -0700 (PDT)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 799D1C14F5E2 for <avt@ietf.org>; Thu, 11 Apr 2024 02:36:56 -0700 (PDT)
Received: by mail-pj1-x1034.google.com with SMTP id 98e67ed59e1d1-2a559928f46so2328578a91.0 for <avt@ietf.org>; Thu, 11 Apr 2024 02:36:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712828215; x=1713433015; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=LVgXPUWIhCGFz4e/GHqs+spvUcLquo6s/4KToa/nqCg=; b=dyD//VGGyERyVmOM0qgPdZEYfyjPmYkJaIUqJ3c6kRRFLlil+GW4KwULGlZFeRQpGZ ZuF9mbM9x5jiUrKLSVByHGynfG+O9AGoUrJO3HnfiOG8vrpgjp+dIYBuYeaHNDPkVofT P+KT86ymLHCaYgKJRbPubuVuEJOixbe+77q5wQrF2sFdXjgZkFlBxCFWJa2BPqHYZfvT Uxz2SRZuAXjfPRRnG5WziD6nHvR+omnMrv9tp2WVrFTOpQRJVsGTsUqSR2Qk8AUYWklR 6q1Y1SQVC7WZF4zCvGzc+V8vppHVdrMssPwENtQzC/7ziikO3dz1nhVqKxeGjeDcvDow u1bg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712828215; x=1713433015; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=LVgXPUWIhCGFz4e/GHqs+spvUcLquo6s/4KToa/nqCg=; b=iPuBgClklh5SMEcs1QFnlDRT2QlIaEUyy3iPjZedXr9JbqsKIchTlWrDwr3mso3+7o c2W8NhgFXuhgBJa8ABc+4ETmIP7KQHf559P2aeohEVg30s5UOHINqZmzIo7XsO+yMm8J E9g2hUZoIIRMrIMuABQME1OW35VAMJuTB9zm9owhEe5MEOhNl9oUMkRmvhj4/bg1ekxe zUa/puHknCKW8MrNAvg7vTbX+6ggZyf8oUMQ704SMlkVcIZgbVdVOfqOIdzhikhGSUwt +G7Yw4s27nfrGynNL5AG6Lf7KLdUYvXMMG2R1Ene2cGaYuFxlFbqlpTWE2bm8zByzq/5 V+SA==
X-Gm-Message-State: AOJu0YznjnlE92KT3fqo7jDQGNRR8S3EqbVeFKuuBjRndy9CJ79BQyXY Ix5wJ4DiXxcvohpHBADN3kQ8sNulMVhjIwvfQTlVZpTDMiELSEWMGFBkBMCQ6c+gFwxq+Xkbi16 bazmvxQGuHMFLmyMzA/Ig9HJDCmE=
X-Google-Smtp-Source: AGHT+IGGLM3Kg8KpxyjAiBs4MQszouYflvLbFXibQVEue3TXhx78p0tIrcUSCWq3l7G9M56Unc1vjx1BI7swA0ZRG1g=
X-Received: by 2002:a17:90a:c291:b0:2a0:20b5:7f1a with SMTP id f17-20020a17090ac29100b002a020b57f1amr5188131pjt.37.1712828215458; Thu, 11 Apr 2024 02:36:55 -0700 (PDT)
MIME-Version: 1.0
References: <f0e95d7c-0385-4206-9605-b3c61cd44b51@alvestrand.no>
In-Reply-To: <f0e95d7c-0385-4206-9605-b3c61cd44b51@alvestrand.no>
From: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Date: Thu, 11 Apr 2024 11:36:44 +0200
Message-ID: <CAEh=tcf_1ZkbixV2y0V3BEVVmgUuVL5vBhjNOVhNxHKC0Qh+ug@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: avt@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005802790615cee506"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/bsmUkA9LkO72YMPr8pitBL6GQys>
Subject: Re: [AVTCORE] RFC 8888 clarification: What does "active" mean?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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, 11 Apr 2024 09:37:00 -0000

Hi Harald,

My interpretation with be interpretation 2 ( the 2nd on your bullet list).
Reasoning: if you have not seen any packet since last report then there is
nothing to send feedback on.

//Zahed

On Tue, Apr 9, 2024 at 2:20 PM Harald Alvestrand <harald@alvestrand.no>
wrote:

> In looking at RFC 8888, we found an interpretation problem:
>
> "RTCP Congestion Control Feedback Packets SHOULD include a report block
> for every active SSRC."
>
> Two easily inferrable interpretations for "active":
>
> - Packets have been seen, and no BYE or timeout has occured
> - Packets have been seen since the last report was sent
>
> Now, the size of the reporting packet is very sensitive to this
> interpretation - back-of-the-envelope says that packets according to the
> last interpretation can be 1/3 of the packets according to the first.
>
> So - which interpretation is intended here, and why?
>
> Harald
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>