Re: Terminology discussion threads

Leif Johansson <leifj@mnt.se> Thu, 13 August 2020 20:46 UTC

Return-Path: <leifj@mnt.se>
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 759983A0780 for <ietf@ietfa.amsl.com>; Thu, 13 Aug 2020 13:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, 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=mnt-se.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 UQgnk9oKRwoh for <ietf@ietfa.amsl.com>; Thu, 13 Aug 2020 13:46:51 -0700 (PDT)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 7B3983A0746 for <ietf@ietf.org>; Thu, 13 Aug 2020 13:46:49 -0700 (PDT)
Received: by mail-lf1-x132.google.com with SMTP id d2so3753193lfj.1 for <ietf@ietf.org>; Thu, 13 Aug 2020 13:46:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=aMLX2HEecp1q6AHMPQ3HBLJKGWYwjpfgTFfVJvJ/wxw=; b=vxgrNyA9Gup+ioyw6VjXuDDvnUhsbGJpJnrTp+DajbtbVsNvwdkXZ5qd0AdOQAjypv 7U1ePHkSuXZuHWWC/5YDB6F3T2GTpA/1RL1LD1d15GDmqAJYlg7Aof285ySY7CwsQV5e 8O87ELQmWK442xtQFGJ1k5yQjaWbN2qx8ZrmeMji6iyH7SKHU0Xd7tTOu/ac0rigeFec cibItlJM+74HwEIVYiNejUM4iBAwG4tN8hCod4VtPsNEhKn+/TG7mLqBjwYGXkiLSrqi JCG8oKvHVyNxExrICW/mgBodgtpDuUBumqiF/1rJcLxHfWEwSVRWPkRFBZjyEjD/ThHQ HYTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=aMLX2HEecp1q6AHMPQ3HBLJKGWYwjpfgTFfVJvJ/wxw=; b=e6hwM0Flwp0xQut9SLhiBNCKX3Y74M/HBAV0HL7jMrBG+/J7EbNbErH4vYlNa1Mu2Y jUztFyzZ35b3Cl5i3MZsIBiM1uKysiF2hMMNOTyG7PypSoQPxuOryS8naYtI7SwfFcmF SYwGZlW7AXde78q7kNe5syDu7BljNe2KE2x4X0iVE5VakjlDso7QX/BQ/ELgCWzWq4Gi UwrEpUgeNb66Fd9GrdvEIoD3tZI/Qru/hhY5ReJzFZ5S/aQhk9FYfBeNTijj3G5mh1f8 Rc/uOGLUGYNb1zrmyzoJLB8sLijiO7tBFe5e9nnbOuu3m1ZHVt731DHxEA1IGFMbCzso HNWA==
X-Gm-Message-State: AOAM533oVi+z9Z5wXtuW36GQ2Oas3V51pfaS6ntIU73U4/gLjYrPWzLK FPdYFjkQe6C5Qb1ZK4nu4dNzgfjiFhc=
X-Google-Smtp-Source: ABdhPJyguRNJXhLbfRSGZpub8nd+aDJwe70LPpmiUYymDjkETKyQBO/KMf/ne02iJ9xI8oywdb0pOA==
X-Received: by 2002:ac2:44d4:: with SMTP id d20mr2982133lfm.137.1597351606889; Thu, 13 Aug 2020 13:46:46 -0700 (PDT)
Received: from [10.0.0.193] (h-98-128-229-68.NA.cust.bahnhof.se. [98.128.229.68]) by smtp.gmail.com with ESMTPSA id e69sm1408451lfd.21.2020.08.13.13.46.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 13 Aug 2020 13:46:46 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-A673D8D2-AAA2-40B7-A9E1-F4C5455477E8"
Content-Transfer-Encoding: 7bit
From: Leif Johansson <leifj@mnt.se>
Mime-Version: 1.0 (1.0)
Subject: Re: Terminology discussion threads
Date: Thu, 13 Aug 2020 22:46:45 +0200
Message-Id: <9A371A86-6572-4B78-9B80-5AD2E7AE5C89@mnt.se>
References: <CAL02cgQzhuO1QeLh5Bbu8k4fPyVeLy-XwRHZLL7575dEgGRc6w@mail.gmail.com>
Cc: Michael StJohns <mstjohns@comcast.net>, IETF discussion list <ietf@ietf.org>
In-Reply-To: <CAL02cgQzhuO1QeLh5Bbu8k4fPyVeLy-XwRHZLL7575dEgGRc6w@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: iPhone Mail (17G68)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XxmYTkhE_HnXy2jReRKUsVKuXTQ>
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:47:01 -0000


Skickat från min iPhone

> 13 aug. 2020 kl. 22:32 skrev Richard Barnes <rlb@ipv.sx>:
> 
> 
> 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.
> 

I hate to point out the obvious but just because you disagree doesn’t make the other side of an argument unprofessional. That way is *dangerous* as it otherizes part of the community. 

The thread in question touched on fundamental questions of language and technology and just because a lot of people (me included) found the topic unpleasant and politically inconvenient doesn’t amount to unprofessional behavior in any way.

Leif

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