Re: Terminology discussion threads

Nico Williams <nico@cryptonector.com> Thu, 13 August 2020 18:35 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4DCE3A0FD1; Thu, 13 Aug 2020 11:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
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 umQhGoYna0s0; Thu, 13 Aug 2020 11:35:56 -0700 (PDT)
Received: from dog.birch.relay.mailchannels.net (dog.birch.relay.mailchannels.net [23.83.209.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A3503A0FC4; Thu, 13 Aug 2020 11:35:55 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 6E949341FAF; Thu, 13 Aug 2020 18:35:54 +0000 (UTC)
Received: from pdx1-sub0-mail-a56.g.dreamhost.com (100-96-8-55.trex.outbound.svc.cluster.local [100.96.8.55]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 8E124341E1D; Thu, 13 Aug 2020 18:35:53 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a56.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.8); Thu, 13 Aug 2020 18:35:54 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Sponge-Abaft: 2211321b426f054c_1597343753945_454309243
X-MC-Loop-Signature: 1597343753945:4092376634
X-MC-Ingress-Time: 1597343753945
Received: from pdx1-sub0-mail-a56.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a56.g.dreamhost.com (Postfix) with ESMTP id 022ED837EB; Thu, 13 Aug 2020 11:35:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=9nt+cVNrbAxG7P MNdr6VbTHlUTY=; b=vvtczmjMJOaqFIKZ9yJlA50f0ptSEU9Yj6FKiskAJjCdnS kl+1dE9nT0ya2kNCTWLCZwmu8gD6J3IZVkEK4msguqqR1xeq9S98ukRlL8BZyJHa G9bKgCJdzwh33jO5AyyMs1iYj5OYuu4ViiWIjSrkT1HkqAMYvRfGKXHCDo3O8=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a56.g.dreamhost.com (Postfix) with ESMTPSA id 960BB837A0; Thu, 13 Aug 2020 11:35:47 -0700 (PDT)
Date: Thu, 13 Aug 2020 13:35:45 -0500
X-DH-BACKEND: pdx1-sub0-mail-a56
From: Nico Williams <nico@cryptonector.com>
To: "Scott O. Bradner" <sob@sobco.com>
Cc: IETF Sergeant-at-Arms <saa@ietf.org>, ietf <ietf@ietf.org>
Subject: Re: Terminology discussion threads
Message-ID: <20200813183544.GF3100@localhost>
References: <9ABDC2BC-E6A3-4249-99C5-F0BB3683A03D@ietf.org> <223A1539-30B0-424A-89D1-A968FFD4C140@symbolic.software> <aceec35c-ccc8-ccca-7a5b-7d23746f67e2@ietf.org> <A9BB633C-3278-406C-BD38-748646D7E454@symbolic.software> <C4BC10B5-6F65-451F-8B15-98AA8D54966A@ietf.org> <E903D378-9FA6-44B7-BDDA-3D283F73039D@sobco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E903D378-9FA6-44B7-BDDA-3D283F73039D@sobco.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: 0
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduiedrleehgddutdduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecuggftrfgrthhtvghrnhepffdtkeethfeuteeviefgfeegjeetjedvhfehgfdvtdefueejheelgeeuhffghffgnecukfhppedvgedrvdekrddutdekrddukeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomh
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GgZSGmVy19gsn91N0NJvfFEjZf4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2020 18:35:58 -0000

On Thu, Aug 13, 2020 at 01:27:31PM -0400, Scott O. Bradner wrote:
> I consider this an abuse of your presumed authority 

The IETF has been abusing its SAA function these past few years.
Download the list archive and search for posts by the SAA and the
reactions to them over the past two years and you should see at least to
previous incidents where the SAA went beyond its remit.  We also had an
AD who very inappropriately doubled as SAA -- those who serve as SAAs
should not serve in any other leadership capacity, and this should be a
hard rule.

The pattern seems to be that once the SAA crosses the line the community
chastises the SAA and then the SAA goes quiet for a year or so.  This
means that every time the SAA goes beyond its remit the SAA function
loses authority and ceases to function effectively.  Now having three
examples of this, might the SAA will learn their lesson finally?  Or
maybe since they insist on misbehaving, the SAA staff should be
replaced.

> in no way should an expression of disapproval of an IESG action be
> considered as a continuation of the discussion that caused the IESG
> action

It's rather unseemly, isn't it, to allow expressions of approval and
disallow expressions of disapproval.  Either the very first expression
of approval should have met with SAA action on account of the Chair's
silence! order, or no expressions of disapproval of the Chair's order
should have met with SAA action.  At most only continued debate should
have met with SAA action.

Nico
--