Re: [bmwg] Murray Kucherawy's Discuss on draft-ietf-bmwg-ngfw-performance-13: (with DISCUSS and COMMENT)

Scott Bradner <sob@sobco.com> Fri, 11 February 2022 13:44 UTC

Return-Path: <sob@sobco.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E6C3A111C; Fri, 11 Feb 2022 05:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.916
X-Spam-Level:
X-Spam-Status: No, score=-0.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PDS_RDNS_DYNAMIC_FP=0.002, RCVD_IN_DNSWL_BLOCKED=0.001, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FdU8yTGxOtyC; Fri, 11 Feb 2022 05:44:15 -0800 (PST)
Received: from sobco.sobco.com (173-166-5-71-newengland.hfc.comcastbusiness.net [173.166.5.71]) by ietfa.amsl.com (Postfix) with ESMTP id 0ECC63A1134; Fri, 11 Feb 2022 05:44:14 -0800 (PST)
Received: from smtpclient.apple (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id F18B21481AD; Fri, 11 Feb 2022 08:44:13 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <5AAFE998-739E-48DA-B82D-2FBCD5989E42@gmail.com>
Date: Fri, 11 Feb 2022 08:44:13 -0500
Cc: IETF <ietf@ietf.org>, bmwg-chairs@ietf.org, The IESG <iesg@ietf.org>, bmwg@ietf.org, draft-ietf-bmwg-ngfw-performance@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <860B04DF-4FAE-4D4C-ADA3-1443CD650FC4@sobco.com>
References: <164386586568.20734.14136987065393258244@ietfa.amsl.com> <fdb1df79-3a53-ea53-8532-ffb8d2545996@eantc.de> <CAL0qLwaDu9U1Kj_GtgNEY6JWpJncyC-t=NYA_uwOHs8zZmCHpQ@mail.gmail.com> <01D0C656-F323-4A7A-BF5B-764D646E2CD8@sobco.com> <5AAFE998-739E-48DA-B82D-2FBCD5989E42@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/3J5SD_hDuAktMqbDAWu9vXuMPTw>
Subject: Re: [bmwg] Murray Kucherawy's Discuss on draft-ietf-bmwg-ngfw-performance-13: (with DISCUSS and COMMENT)
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Fri, 11 Feb 2022 13:44:28 -0000

if every implementor were so disciplined it would not be so bad but, I fear, far too often
an implementor views a SHOULD as something that is not important enough to be a MUST
so I do not have to worry about it

at least the document author should say what could go wrong if its not done 

Scott

ps document authors should take to heart the following from 2119

6. Guidance in the use of these Imperatives

   Imperatives of the type defined in this memo must be used with care
   and sparingly.  In particular, they MUST only be used where it is
   actually required for interoperation or to limit behavior which has
   potential for causing harm (e.g., limiting retransmisssions)  For
   example, they must not be used to try to impose a particular method
   on implementors where the method is not required for
   interoperability.