Re: Terminology discussion threads

Richard Barnes <rlb@ipv.sx> Thu, 13 August 2020 20:31 UTC

Return-Path: <rlb@ipv.sx>
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 17C693A0486 for <ietf@ietfa.amsl.com>; Thu, 13 Aug 2020 13:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.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 PH-s5Klwjwae for <ietf@ietfa.amsl.com>; Thu, 13 Aug 2020 13:31:28 -0700 (PDT)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 4A31B3A0B5C for <ietf@ietf.org>; Thu, 13 Aug 2020 13:31:28 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id n129so6431524qkd.6 for <ietf@ietf.org>; Thu, 13 Aug 2020 13:31:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FCurGAFXV9X4jUxm2ZCwPru+qzppPffS1Ma7K344aH0=; b=l4VY7bjRN7+areo6Sf6xUcIAg5sv9BDe10fD/34cPMDoXXRal8pOO8Ib8Hk8vlfjoL UPYf4+DAZS1y3mnrlCXbEwA9U5Nx45Z8qKkOKT1fojzB6dK3636tquhh9PuvlkJvzSDJ c9CskS+zVM/V3RAO51XWZIgAQnKEvd27EH+9+7r8P6sS+b0kSJ26Zc7VzeXTSn9CqIDY yPHcEuxO+GR4hy6zaakd4iVnX5zyCvNdZzHsdH9khuKeSxEQoO74DklzwMf3EoYW1BaU ckRmpLloou45zn1wbFWWB1PlNYgLAS4a8TmwIDtMbMDstXGJh5jqOgNdPEawMewe3JNW fCSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FCurGAFXV9X4jUxm2ZCwPru+qzppPffS1Ma7K344aH0=; b=liHhhnBHM2kiWxiOFFXQfSTmyrJi25MXpA5at0z099PpbYpKd9AQ8hUbk+4neU93Tq CTFo8nAWf1rQaZAn5eDn+9QEg1GBOpqeCmhMcgRkpLOyA+q4QmeX0YoW1VCHDiF75Fk5 gXszvaDX03B4dRhKEapgxNT/JZJ9LXWrDDdwa9Jetyl9EHlNha1pr5iM6gZkvvR80p0X kcNXtIlHgXag0Ze5kdTtf5tzovIGw4PpgdU3Ixgtpv+Gnh9ObnqwZe7e6ohEECbI0e+m oQILzhxy8EVWmZ1RETgtvOaNIYTntDkfO+QUs89N7UHD33CLPM41PZqi/870KT7+35nD P0qw==
X-Gm-Message-State: AOAM533O+h3Lc9qtGpNBGv+t+rWXWNTkgUBOghRyliqWeUL4/i9nli6y 5ZJ8WzWctfFoCGfGqDfI2C70A8X1bcwWXPy/r9wuvg==
X-Google-Smtp-Source: ABdhPJxymoTinfL7vyDj5o7vJ7rI4Pa0nGWlWZUEjyuncrhkeaGCUh/ApERMoX1tB5OkGTHiOMvePxdNjF2hL1KZIiM=
X-Received: by 2002:a05:620a:63a:: with SMTP id 26mr6538414qkv.490.1597350687186; Thu, 13 Aug 2020 13:31:27 -0700 (PDT)
MIME-Version: 1.0
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> <m2sgcq4fq1.wl-randy@psg.com> <20200813181549.GA27732@faui48f.informatik.uni-erlangen.de> <6EDEF995-7D31-42D4-83C7-B9C406962516@gmail.com> <20200813194819.GB14418@faui48f.informatik.uni-erlangen.de> <3af06ea0-5702-e357-2177-ea7de38f09c3@comcast.net>
In-Reply-To: <3af06ea0-5702-e357-2177-ea7de38f09c3@comcast.net>
From: Richard Barnes <rlb@ipv.sx>
Date: Thu, 13 Aug 2020 16:31:11 -0400
Message-ID: <CAL02cgQzhuO1QeLh5Bbu8k4fPyVeLy-XwRHZLL7575dEgGRc6w@mail.gmail.com>
Subject: Re: Terminology discussion threads
To: Michael StJohns <mstjohns@comcast.net>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004ab58c05acc830ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lRe6seCzHDQJxF-2Ncg3L2gz9bI>
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 20:31:32 -0000

RFC 3005 says plainly:

"""
   Inappropriate postings include: ... Unprofessional commentary,
regardless of the general subject
   The IETF Chair, the IETF Executive Director, or a sergeant-at-arms
   appointed by the Chair is empowered to restrict posting by a person,
   or of a thread, when the content is inappropriate
"""

Given the level of unprofessional discourse in the muted conversation,
muting the entire topic seems like an entirely appropriate recourse.

--Richard

On Thu, Aug 13, 2020 at 4:26 PM Michael StJohns <mstjohns@comcast.net>
wrote:

> On 8/13/2020 3:48 PM, Toerless Eckert wrote:
> > At least there seems to be sufficient +1 from distinguished community
> > members such as current or past IAB, IESG members, IAB Liaison, IETF ISOC
> > appointee, IRTF and NomCom chair to hope that the action taken was
> rightfully
> > within the privilege of IETF chair according to the rules.
>
> Mike StJohns, Past IAB, Past Nomcom Chair
> Scott Bradner, Past IAB, Past Area Director
> Randy Bush, Past Area Director
> Charlie Perkins,  Past IAB
>
> (sorry if I've missed other roles...)
>
> So what's your point?
>
> In any event, my opinion is that this action was NOT taken "rightfully
> within the privilege of the IETF chair according to the rules", but I'm
> withholding further judgement until the Chair responds to my request to
> clarify which part of 3005 they believe applies and grants authority for
> a mass PR threat.
>
> >
> > If this step was ultimately determined (by whom... ?) not to be within
> > the privilege of IETF chair then i am bit worried about what i would
> > have to think about all those +1.
>
> I'm not sure why.  Everyone has opinions.  Some are more useful than
> others, and each of us will have an opinion on that topic as well.
>
>
> Later, Mike
>
>
>
>
>