Re: Terminology discussion threads

Bob Hinden <bob.hinden@gmail.com> Thu, 13 August 2020 18:59 UTC

Return-Path: <bob.hinden@gmail.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 D29B13A1048; Thu, 13 Aug 2020 11:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=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 (2048-bit key) header.d=gmail.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 eYkx3-9hwmbV; Thu, 13 Aug 2020 11:59:17 -0700 (PDT)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E94D3A104A; Thu, 13 Aug 2020 11:59:17 -0700 (PDT)
Received: by mail-wm1-x32a.google.com with SMTP id 184so5972943wmb.0; Thu, 13 Aug 2020 11:59:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=THFMIXVw3xVVw5Dlm9dxas8kBU7CwaOyM11nCbH4wj8=; b=QODGfPKq4imvJzV6StA7GfDjjffW6eK26sKNVEB4fKjuVQhsTU+WwLP9dAtbqgZhTP WQbKW1DESCOqABNPWFpFYnkH6XgSHHgSkybi8c+ZPXlGDZX6TOJzUHVEu8tDGnPfD/5G /JtWazm2z8p/ZKtV8jIjo/C0ijcsJtO8MKyfuPdLKoAyii1vI0iSsHP/drEGiAXWm1sH 0av0zB3wdRm8qaXK7j4O2zAggpytMBXwHFJJ/FRxA08hkbgydaq60e1kHO8IPlfFqFZ5 lx3GyB+L/mnI4LdCXY3zn+L7T29hXNnIuvucUq7ARiTosn3Q0V5xdTtFey9XTrJcaPcZ RI3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=THFMIXVw3xVVw5Dlm9dxas8kBU7CwaOyM11nCbH4wj8=; b=VL+0jRhhbIFuhrRVUuL8U5vpLRWa7LM7FyOZ8eOy0uCSEeViFV926I/j292FsmSffB iJrqOMoNQtc9d1McaubmOcI30XBjTAzfs9DOxdufcUY1Y1nq4G90ozKlfu18RGAOT57C 3jWOwTS1r+TmVXgcwu5Qy1h/LSfF+bqoJ4lwTbExNGp0vR3Fe3oYfxXsMmObthwZgQMn 2oS6LP3CH/4YsIc6cdaYtjLgNGxVgTa/q8ZZn24Q/oNJxTHoE/0rZWmoYa4aTQxNEEz8 TgMgvDvuOMizWSEr4Uw4Ma+3nyM4Wixt3AnPh0j7R+/1n9TLEq9lOkeFMRE6ZLReV/Tm ScgA==
X-Gm-Message-State: AOAM531doq8mUm1U2C4Wd3ezziGVW5ye3Z+DoqMBB9+1Ctg59lWl5De7 kNiVr8qA3v6fyzhYJkpnOB0=
X-Google-Smtp-Source: ABdhPJzNx/IHd1U3scqZrV8R8xixEHKAQQl8hmXMYCcbtgefVQ0HV8X0MGH4CgfBEfm9ikaoFC47ig==
X-Received: by 2002:a1c:e244:: with SMTP id z65mr5562535wmg.34.1597345155501; Thu, 13 Aug 2020 11:59:15 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:2cb8:296e:8d9a:1674? ([2601:647:5a00:ef0b:2cb8:296e:8d9a:1674]) by smtp.gmail.com with ESMTPSA id h7sm10977617wmf.43.2020.08.13.11.59.13 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Aug 2020 11:59:14 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <2E198038-97DA-4B71-91E7-49B9106D4EFF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_AE5BC918-8B7E-4D66-A296-C4FF0BAA336E"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
Subject: Re: Terminology discussion threads
Date: Thu, 13 Aug 2020 11:59:06 -0700
In-Reply-To: <20200813183544.GF3100@localhost>
Cc: Bob Hinden <bob.hinden@gmail.com>, Scott Bradner <sob@sobco.com>, IETF Sergeant-at-Arms <saa@ietf.org>, IETF <ietf@ietf.org>
To: Nico Williams <nico@cryptonector.com>
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> <20200813183544.GF3100@localhost>
X-Mailer: Apple Mail (2.3445.104.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ex8zAP9kkXt3UQF39oPMGRn6Oso>
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:59:19 -0000

If anyone has feedback on the current leadership, please let the NomCom know.  See:

https://datatracker.ietf.org/nomcom/2020/

According to this page, they will be asking for feedback on

	Wednesday, October 14, 2020: Call for community feedback

Bob


> On Aug 13, 2020, at 11:35 AM, Nico Williams <nico@cryptonector.com> wrote:
> 
> 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
> --
>