SaA Team actions (was: Re: Terminology discussion thread)

John C Klensin <john-ietf@jck.com> Fri, 14 August 2020 01:39 UTC

Return-Path: <john-ietf@jck.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 C41593A0BE6 for <ietf@ietfa.amsl.com>; Thu, 13 Aug 2020 18:39:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 D5Jfp37KHfvz for <ietf@ietfa.amsl.com>; Thu, 13 Aug 2020 18:39:54 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99EF23A0BE3 for <ietf@ietf.org>; Thu, 13 Aug 2020 18:39:54 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1k6OhE-0009os-VK; Thu, 13 Aug 2020 21:39:52 -0400
Date: Thu, 13 Aug 2020 21:39:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: IETF discussion list <ietf@ietf.org>
Subject: SaA Team actions (was: Re: Terminology discussion thread)
Message-ID: <8AC098EC9B3D4711F4203D0F@PSB>
In-Reply-To: <12c0908c-316c-c1e8-ddb9-49dc6b40d23d@gmail.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> <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> <12c0908c-316c-c1e8-ddb9-49dc6b40d23d@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bRphtIF4bHE1CSTP76RKKsl_7ww>
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: Fri, 14 Aug 2020 01:39:56 -0000

Brian,

Thanks for posting this.  Rather than say "+1", I want to
emphasize two things in your note and expand a bit on one of
them.  First, I agree that the discussion had gotten out of hand
and that it was entirely reasonable and appropriate for the IETF
Chair to request people to hold the discussion for a while or
take it elsewhere.  However, the key word is "request".  I am
not aware of anyone, at any time in the IETF's history, having
the authority to shut down a discussion topic that is clearly
relevant to the IETF (if it were not, the IESG would have been
out of line for starting the discussion).  As Mike points out,
we have assorted remedies for individuals who repeatedly
generate off-topic, disruptive, or otherwise problematic
postings, but those are about individual behaviors, not subject
matter.

So, it seems to me that there are two possibilities.  One is
that the SaA team has shown extremely bad judgment in their
interpretation of what constitutes disruptive or inappropriate
behavior or that they misunderstood the scope and implications
of the IETF Chair's recommendation (not only in Nadim Kobeissi's
case but in the only slightly less clear case of Lloyd Wood on
the same subject matter)  and should reconsider and explain
their position.   The other is that this was actually done at
the specific direction of the IETF Chair, in which case I think
the specifics of that direction should be made public to the
community so we can all evaluate whether our discussions of
these actions are still appropriate in the IETF.

   john


--On Friday, August 14, 2020 09:16 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> 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
>> 
>> 
>> 
>> 
>