Re: Recent threads concerning sergeants-at-arms

Keith Moore <moore@network-heretics.com> Tue, 03 September 2019 13:49 UTC

Return-Path: <moore@network-heretics.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 7EE47120118 for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2019 06:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 puybh-jmYcls for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2019 06:49:52 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C799212001A for <ietf@ietf.org>; Tue, 3 Sep 2019 06:49:52 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 26A872208C; Tue, 3 Sep 2019 09:49:52 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Tue, 03 Sep 2019 09:49:52 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=LOdsrO uMc9AN4v+3HQ3tcPjN0BPWjzIVHc/r+lAC3AM=; b=Uw1i8o4cx06UAECryTndFF 4lbYpfhGfF5XWP6jzinlkx4o/iqjNioebuXuH3S5Iiv0LUseR4FCTKC+XYVvBZUI B19uMdqyR/OSzzzUgKUyhCUTy+zSDQHAtBxE4WVjKahsMQmOGK89IhXrRUWgdDug KjxWgXdGtMaZmXfzPzVuJVJ2mX5fAv8x9BZzizN+cpBcVEmOzXt+Q9nisO+paDcw ICvDaJjt3fAM2JjJGJYp0VdjkKeelRJZqWOcDq3rEB0xPl/11ROtVOHBx50nYRNA cYX6oXpjh1evwy1zNAhpyTUbdccKUTx/Y/hh3HwmCQqBrz3mmCuWmoSxYl/KL3Wg ==
X-ME-Sender: <xms:fW9uXfBVGfBnPuZahVUAEU8pGRehD2ioEE8ByRsEmwA19BAhSJkiaA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejfedggedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgesrgdtre ertdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrdduhe enucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgv thhitghsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:fW9uXdKv9k501xIAfLQQh9InNWM7mCLlYNl34GXYi1kVu6hJ8xGyMw> <xmx:fW9uXayPYIjn49tMIO96sI2hbqU8_bo1aZUx4GGxETGQGsTG4tTN4w> <xmx:fW9uXZyZg9P0A8umQHht8JGDdHORRAFWE6lebueP0WchHn5LK6v8tw> <xmx:gG9uXc92Ja_kH0uzaSYd2wqFYo4akLlXgixMtNQarTBanZllVAzjqQ>
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id DC81C80063; Tue, 3 Sep 2019 09:49:48 -0400 (EDT)
Subject: Re: Recent threads concerning sergeants-at-arms
To: ietf@ietf.org
References: <2D3C4495-F61A-4616-82B7-4A7AF36EC282@cooperw.in> <CABcZeBOpMvoxmE3BK-s65cGr0k1x3CyjzjCXPyHnV2bUPrn9QQ@mail.gmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <63d774fb-f09e-1fc4-f139-53102c332eaf@network-heretics.com>
Date: Tue, 03 Sep 2019 09:49:47 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBOpMvoxmE3BK-s65cGr0k1x3CyjzjCXPyHnV2bUPrn9QQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------DE1DB289179D4928AFA1548B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wVyA5Cxi1Ac0hphi0MFI5b3oFI4>
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: Tue, 03 Sep 2019 13:49:57 -0000

On 9/3/19 9:31 AM, Eric Rescorla wrote:

> On Mon, Sep 2, 2019 at 6:52 PM Alissa Cooper <alissa@cooperw.in 
> <mailto:alissa@cooperw.in>> wrote:
>
>     But all of this work will take time. In the interim, we will all
>     continue to feel our way through in an extremely gray area where
>     what seems like an obvious right answer to one person seems like
>     an obvious wrong answer to another. During this interim period, a
>     personal wish of mine would be to not have every message sent by
>     the SAA challenged and adjudicated on ietf@ietf.org
>     <mailto:ietf@ietf.org>.
>
>
> I wanted to pull out and amplify this point.
>
> We have a system which incorporates a lot of points of escalation for 
> bad decisions (appeals, the main ietf list, plenaries, recalls), and 
> many of those mechanisms have low thresholds for activation. If every 
> action by leadership (and for the sake of this discussion I'm 
> including the SAA in leadership) is escalated, the system will quickly 
> grind to a halt. What keeps it running even as smoothly as it does is 
> that people mostly adhere to the norm of escalating only when really 
> necessary.

All true.  But the SAA is a fairly unique threat.   They're not only 
empowered to shut people down, they also operate without transparency or 
real accountability.  When the SAA is found to have grossly exceeded 
their authority under 3005 (which does appear to have been the case), 
and the IETF leadership doesn't immediately address this problem, it 
undermines trust in the organization and the leadership.

And all of this is taking place in the broader context of an effort, 
apparently endorsed by some of the leadership, to promote censorship of 
IETF input for arbitrary reasons.

To say this is chilling is a tremendous understatement.

I am looking for some sign that leadership takes these problems 
seriously and will rectify them.   So far what I see looks like efforts 
to sweep them under a rug.

Keith