Re: IESG Statement On Oppressive or Exclusionary Language

S Moonesamy <sm+ietf@elandsys.com> Fri, 07 August 2020 21:24 UTC

Return-Path: <sm@elandsys.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 974303A0B44 for <ietf@ietfa.amsl.com>; Fri, 7 Aug 2020 14:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 LP6Lske2g-_1 for <ietf@ietfa.amsl.com>; Fri, 7 Aug 2020 14:23:59 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 162023A0B46 for <ietf@ietf.org>; Fri, 7 Aug 2020 14:23:31 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.180.98]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 077LNDec014915 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Aug 2020 14:23:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1596835406; x=1596921806; i=@elandsys.com; bh=k/Ee2anh9NTL7Cbs6IapRokxDBoxd8qDZFjUVPDU1w4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QyFGUjmrQnT49SWAgLHxr9rv6a+PO8j7IQNgFol+5OnINbQfES+XXRwsoBr8uDexr uxQbJbIfjCYlfBkdBSY40nDa9ROh9ppvSgC2wUk3y3Eh4ZGdojpHzaguDLalibAcB4 HPnaur1z39jt1IlHl//GkjpjomhoUw6j7kb6GrDg=
Message-Id: <6.2.5.6.2.20200807130132.0d747fe8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 07 Aug 2020 14:19:07 -0700
To: Dan Harkins <dharkins@lounge.org>, Viktor Dukhovni <ietf-dane@dukhovni.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
In-Reply-To: <afd6e8e6-4da9-5ebe-f8a7-3e0f1e800f3e@lounge.org>
References: <5692e18e-afbb-9294-1074-3b81dafe8803@network-heretics.com> <59C4CA26-A1EB-4CF4-B973-BC2BBF53A094@gmail.com> <CAL02cgTZt-9+QWPT1aWXcOgpEwuNV2uHnVi5dGm7V5y_8_U1SQ@mail.gmail.com> <0cceb0f2-b5fe-a194-7ce8-68cc537f9cd1@lounge.org> <CAL02cgTV-cfTPO2wrKz0H2E=FLhagu-qs7fwx6jXeJDH-2cSHA@mail.gmail.com> <6fc4abe2-5343-e625-f2e7-ecfb52f91764@lounge.org> <CAL02cgR1wa8ssgsiLaG+uFKOh+7xZGuWtmxWa9HY5y+6pnRYLw@mail.gmail.com> <afd6e8e6-4da9-5ebe-f8a7-3e0f1e800f3e@lounge.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TI3ffk3lwfRZfyt3jp0vfCWSIWY>
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, 07 Aug 2020 21:24:03 -0000

Hi Dan, Victor,
At 11:43 AM 07-08-2020, Dan Harkins wrote:
>Â  Oh please, spare me the [removed] privilege schtick. We both know
>what we are talking about and that is the discussion on
>draft-knodel-terminology and whether ON THAT TOPIC you are in the
>"in crowd" or the "out crowd".
>
>   You know what else is privileged? Company affiliation! I noticed my
>opinion at IETF was discounted considerably when I left Cisco for a
>start-up. Not part of the influential crowd anymore. So I'm keenly
>aware of privilege at the IETF, don't worry about that.

The discussion (please see topic) in another 
venue, which is unrelated to the IETF, turned 
into a United Stated v/s rest of the world 
arguments.  I didn't understand why you took a 
strong position until I read your latest 
messages.  For what it worth, I understood some 
of the arguments in your review, e.g. the $64 
required to access the first two references.

>>3. You keep demanding evidence, even after 
>>several people have agreed there is a problem 
>>here.  There's a word for this style of debate: 
>><https://en.wikipedia.org/wiki/Sealioning>https://en.wikipedia.org/wiki/Sealioning
>
>   Oh, so several people agreeing closes off discussion, no evidence needed,
>just a "I'm standing up for the little guy".
>
>   I guess those several people are in the "in crowd", the privileged ones.
>They are so privileged they merely need to refer to their existence to
>squelch debate. Impressive!

It was customary to close a discussion or ignore 
a question when someone asked something which was 
inconvenient, e.g. a modicum of data, evidence, 
etc.  I came across that for 7704.  There is more 
than one problem in the thread.  I would not bother to locate them.

At 10:15 AM 07-08-2020, Viktor Dukhovni wrote:
>This thread was not here until recently, and yet throngs of newcomers
>were not then clamoring to join the IETF then, who are now staying away
>(for reasons other than COVID-19 restrictions).  The discussion has
>actually been mostly tame, at worst at times somewhat pedantic, with a
>bit of sophistry here and there, but likely even mellower than on some
>of the more contentious technical issues.

There isn't any evidence that newcomers stayed 
away because of this thread.  At the same time, 
it is unlikely that someone new to mailing lists 
would post a message on the thread.

Regards,
S. Moonesamy