IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 11 February 2022 14:06 UTC

Return-Path: <mcr@sandelman.ca>
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 15AA63A0F0E; Fri, 11 Feb 2022 06:06:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 UMqclQ8rYWXm; Fri, 11 Feb 2022 06:06:11 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30E9A3A09DD; Fri, 11 Feb 2022 06:06:11 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [142.169.78.206]) by relay.sandelman.ca (Postfix) with ESMTPS id 59A3B1F489; Fri, 11 Feb 2022 14:06:08 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 61B621A01AD; Fri, 11 Feb 2022 09:06:06 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Scott Bradner <sob@sobco.com>
cc: IETF <ietf@ietf.org>, bmwg-chairs@ietf.org, The IESG <iesg@ietf.org>, bmwg@ietf.org, draft-ietf-bmwg-ngfw-performance@ietf.org
In-reply-to: <01D0C656-F323-4A7A-BF5B-764D646E2CD8@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>
Comments: In-reply-to Scott Bradner <sob@sobco.com> message dated "Fri, 11 Feb 2022 07:08:23 -0500."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 11 Feb 2022 09:06:06 -0500
Message-ID: <656115.1644588366@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/XKz2VlVKOSatAmj-R4Pvdpw53xs>
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 14:06:17 -0000

Scott Bradner <sob@sobco.com> wrote:
    > speaking as the editor of RFC 2119

    > nice chart of how to misuse SHOULD but - imo - SHOULD is a MUST with an escape clause

    > I do not think it is useful to use SHOULD without specifically saying
    > what the escape clause is -
    > i.e. specifically say when its OK to not act as if it was a MUST

I've gotten caught by this regularly.

I don't want to write MUST because if feels rude to be so demanding, and I
can envision *some* escape clause, I'm just not yet sure what it is yet.
That's wrong on my part.

    > (if I had to do it all over again I would not have included SHOULD/SHOULD NOT)

It's hard to imagine some other word that would allow for the escape clause.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email