Re: Terminology discussion threads

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 13 August 2020 21:16 UTC

Return-Path: <brian.e.carpenter@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 5DEEE3A077C for <ietf@ietfa.amsl.com>; Thu, 13 Aug 2020 14:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.048
X-Spam-Level:
X-Spam-Status: No, score=-2.048 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, FREEMAIL_REPLY=1, NICE_REPLY_A=-0.949, SPF_HELO_NONE=0.001, SPF_PASS=-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 wl6QkSkSbEOk for <ietf@ietfa.amsl.com>; Thu, 13 Aug 2020 14:16:43 -0700 (PDT)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 A6D753A0766 for <ietf@ietf.org>; Thu, 13 Aug 2020 14:16:43 -0700 (PDT)
Received: by mail-pl1-x631.google.com with SMTP id t11so3194364plr.5 for <ietf@ietf.org>; Thu, 13 Aug 2020 14:16:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=CLQtnboRGB/Vy6h07XGFTDOFaFt/olCbhHXrNsqi92Y=; b=az4083lmzLfYDAlSHiCC/QAtQROf0gIluAM0DVfRweLp6HTlO72EMM3kkRRu6T+p9B d4H7Ded3OR5RU+BLNX1zOISa7YEdP+XE0An6Kx+Cl4caSdKg3bhAuKBYrc+p2DkIwOhV V5ed7MREXJS67NWLcmT3nKipm57wMEv96/MxTZRWz5g0OdwUS3M4ocoHvLmRZgzMsIOw mJ38p6NZUHwHmEravxIiFsCaxokIEI6wYxeNodAYPIj9p4qEMj4qWOE+jCq+lQTE9QVo BDO3kEq1jAqqa65pAjQrjrdEV5UwP2iT4xutdWDGtSwc+9xBsnrkOFQwuV9fXIXdxkFA Uh2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CLQtnboRGB/Vy6h07XGFTDOFaFt/olCbhHXrNsqi92Y=; b=fZimhq6LIRRFz+Zar3O5MeLk2eNYiHYzU2WTm5rwXxm6POV/fuy083J3U9cTPVQ1pt S3gfCaOIszxioYjNTjdf8oJKB+0isBnmCu2QBGNPOGjEM7P8Ou37+f7FU/MOZWjATqHM e7DJudATO/sALzxsHe4E0sZ/K+8G2WIY3JJlZoj4pI7e+Qtfay3bcbeH5WM+YY20AtM9 MomtQFfBRcw9Hhw5RU/ln0/vqD9s78JKcDLfkfXPafMyBKIBHT2VIjYyrVgN7X/tXOE4 obOKOMwDDINQaxgaRS52whT/05hOy2vTJs9NJYg1QsAZb8bBg2/sjC9v+aIRwQ5MBFAW hF+A==
X-Gm-Message-State: AOAM53208yMiVRYZoL4IFmwlD8pvCSRfNLQcGTi3JAM8fqgH1rBLEwsI x2WxykTehNVs5zDUj7vXSoxggqbhNWg=
X-Google-Smtp-Source: ABdhPJwI9FkjBc6fhL+6p/TUY7Cakaz8lcE3BuzyntN0S/bXjlalG7QWOOpa4EsJopHBCKUBnMEVDA==
X-Received: by 2002:a17:90b:3008:: with SMTP id hg8mr2315442pjb.120.1597353402806; Thu, 13 Aug 2020 14:16:42 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id l62sm6155922pjb.7.2020.08.13.14.16.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Aug 2020 14:16:42 -0700 (PDT)
Subject: Re: Terminology discussion threads
To: Richard Barnes <rlb@ipv.sx>
Cc: Michael StJohns <mstjohns@comcast.net>, IETF discussion list <ietf@ietf.org>
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> <CAL02cgQzhuO1QeLh5Bbu8k4fPyVeLy-XwRHZLL7575dEgGRc6w@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <12c0908c-316c-c1e8-ddb9-49dc6b40d23d@gmail.com>
Date: Fri, 14 Aug 2020 09:16:38 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAL02cgQzhuO1QeLh5Bbu8k4fPyVeLy-XwRHZLL7575dEgGRc6w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BheHFnKLLiozVM6i6-watW83l4Y>
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 21:16:45 -0000

Richard, I think you are confusing two distinct points.

1. The thread that resulted from the IESG's own posting had become utterly
pointless since it consisted entirely of two sides of the question repeating
themselves. It was quite reasonable for the IETF Chair to request people to
refrain and to take the discussion of the only relevant I-D (whatever its
merits) to the most relevant WG. I'd probably have done the same thing
in her shoes.

2. Now the SaA team has chosen to censor Nadim Kobeissi for presuming to
challenge that action. As far as I can see, Nadim's postings IN NO WAY
qualify as "a pattern of abuse". There are four in total. The two under
the subject "Terminology discussion threads" are principally about IESG
actions, not about the original topic. The second one is deeply sarcastic
but I think we all understand why. The two under the subject "IESG
Statement On Oppressive or Exclusionary Language" are IMHO quite useful
contributions compared to most of that thread,  and they were sent well
*before* the IETF Chair's request to refrain from the discussion, and
therefore cannot legitimately be considered by the SaA.

In my opinion the SaA had absolutely no grounds to censor Nadim; to
the contrary he was saying something important about the IESG. I hope
he's aware of the appeal process.

Incidentally, the SaA message included the phrase "against the direction
from the IETF Chair." It's certainly true that the Chair can give directions
to the SaA team, but the Chair can't give directions to the IETF; as Fred
Baker used to say, "I'm called the chair because everybody sits on me."

Regards
   Brian Carpenter

On 14-Aug-20 08:31, Richard Barnes wrote:
> 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 <mailto: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
> 
> 
> 
>