[bmwg] Martin Duke's Discuss on draft-ietf-bmwg-evpntest-09: (with DISCUSS and COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Mon, 28 June 2021 23:49 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: bmwg@ietf.org
Delivered-To: bmwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 53E933A1BF2; Mon, 28 Jun 2021 16:49:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-bmwg-evpntest@ietf.org, bmwg-chairs@ietf.org, bmwg@ietf.org, Sarah Banks <sbanks@encrypted.net>, sbanks@encrypted.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.33.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <162492415876.27898.6388420658647697068@ietfa.amsl.com>
Date: Mon, 28 Jun 2021 16:49:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/2cxYe-BWc3BOSUW3GE3nHDYM2UE>
Subject: [bmwg] Martin Duke's Discuss on draft-ietf-bmwg-evpntest-09: (with DISCUSS and COMMENT)
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jun 2021 23:49:20 -0000

Martin Duke has entered the following ballot position for
draft-ietf-bmwg-evpntest-09: Discuss

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-bmwg-evpntest/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

(3.8) (4.8) Why is packet loss measured in time? How is learning 2X MAC
addresses relevant to the packet loss measurement at the traffic generator? How
long does the traffic generator have to wait to conclude that the packet is
lost?

(3.9) Is a single failure to learn an address sufficient to determine that the
device has reached capacity? Or could packet loss or some other phenomenon lose
some addresses? In other words, be more precise on how polling reveals the
capacity.

Is there some lower bound on the time between sending ARP/ND packets and
querying the DUT?

(3.11, 3.12, 4.10, 4.11) Does the traffic generator send F frames in total or F
ffs? The spec says both. Are there any constraints on F, perhaps an integer
multiple of X?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(3.10, 4.9) Again, is there a minimum time between sending the traffic and
querying the result?

(3.12, 4.11) I don’t believe you’ve adequately addressed Al’s TSVART review.
What does “100% compared to the average usage” mean? Is that double? Shouldn’t
there be a formula to compute average usage?

As Al asks, what is the threshold over which an increase in memory usage will
fail the test?