Re: IESG Statement On Oppressive or Exclusionary Language

Joseph Touch <touch@strayalpha.com> Mon, 27 July 2020 16:28 UTC

Return-Path: <touch@strayalpha.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 6C1D43A1B7A for <ietf@ietfa.amsl.com>; Mon, 27 Jul 2020 09:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level:
X-Spam-Status: No, score=-1.318 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 ekypAidSLt82 for <ietf@ietfa.amsl.com>; Mon, 27 Jul 2020 09:28:46 -0700 (PDT)
Received: from server217-4.web-hosting.com (server217-4.web-hosting.com [198.54.116.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2BC73A1B67 for <ietf@ietf.org>; Mon, 27 Jul 2020 09:28:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=aSSsUdLJFQSXBtpbwg+DOZP4r+Mk0rIUn0qRRBkCYrw=; b=YcLkOGlfLjPQLhov4I9VOg9iF CZsqznVP4WCb7RYT9kw4MdJVzcZHW2yekKth3NfgI9l3I1TrE5fYkw+yFuoukf3eaYqM+WHN5RwDy ALlpH0m0NrOYa38sFrxEahPCxG13diOYBLNQ/fHbv+PtmXB8mW080/qJp5DxH6i24CuwMcvjNgcmR BfQr+D3JUkTaCna3tM/3O3QAvmDg0K5e59LwPQmo1oTYiaZ8geLKOQu8o6w5WJfK11Lxcz/3xysD6 tcOdFy/WXNwB0Q/JZvqSW/3xu6FvgXwg8h0uOzzXAlFqWTbOIUSSsjUADTnBkZYR7Oj7DdmF4KQkd CROCLc2oQ==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:59625 helo=[192.168.1.14]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <touch@strayalpha.com>) id 1k05zV-0017ks-Uv; Mon, 27 Jul 2020 12:28:46 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_F6833E35-76B1-4EF1-B5D0-55AFE01D8415"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <19456FE4-8781-4F4E-943B-9A430080A0E8@gmail.com>
Date: Mon, 27 Jul 2020 09:28:41 -0700
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Message-Id: <63692C48-CFDF-42F4-A704-3C063293174E@strayalpha.com>
References: <159552214576.23902.6025318815034036362@ietfa.amsl.com> <1cfa41c4-2877-2462-e5cc-325e67056d00@lounge.org> <2d8a103d-61b9-5ba0-c77f-d6b730eb982a@joelhalpern.com> <7ec1f6fe-8cb8-341e-ca07-b411a0a64795@lounge.org> <43EC74C0-589E-43DA-9F84-73D7B9F218CE@akamai.com> <526464f6-b82a-688b-cfaf-5a7e28ae18b0@lounge.org> <E16E1747-984B-4530-A9FD-7B59DA6F49E5@akamai.com> <1ae2ff5e-09e9-d230-a96b-763d4290d5e2@lounge.org> <972E831C-265A-4297-BAE3-7F167946FC78@akamai.com> <d13a2085-172a-e92c-6b12-c9d61ed384b5@lounge.org> <D5CC0F87-FF6A-4824-B930-A43875C2FF1E@akamai.com> <d7604baf-7caf-85d3-21af-b765295951f1@lounge.org> <E9923B2A-7A94-4EA1-9890-16801D82285D@akamai.com> <19456FE4-8781-4F4E-943B-9A430080A0E8@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cHq1Huvs9P5I9qbG-bah_4Ybrj4>
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: Mon, 27 Jul 2020 16:28:49 -0000


> On Jul 27, 2020, at 9:08 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:
> 
> 
> 
>> On 27 Jul 2020, at 15:50, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
>> 
>>>    And I'm telling you that if you that the bar to compel speech is 
>>>   considerably
>>>   higher than rank assertions and fallacies.
>>> 
> 
>> Nobody is compelling anything,
> 
> The subject of this thread is “IESG Statement On Oppressive or Exclusionary Language”. Someone is definitely tryiing to compel people to not use what they consider to be oppressive and exclusionary language.

The doc says:

	Authors SHOULD … (avoid the following terms)
	RFC Editor MUST … (support this process by offering alternatives)

I.e., the only compelled party here is the RFC Editor - at best to provide suggested alternatives.

> ...
> IETF consensus is usually achieved by a small group of people who care about a particular subject.

That’s how the IETF works. If you want to change process, that’s a different doc.

> This doesn’t work here. Like every other topic, only the people who care about word usage are going to participate in the discussion, and maybe Dan and two others will be the only voices there against it. The people who don’t care so much, or the people who think the whole thing is just silly are not going to participate.  Yet this will end up in an RFC that is binding on everyone.   

That’s true of all IETF docs.

> The potential for a small but motivated group to hijack the process and dictate policy is great, and the argument that the process was open to everyone is not convincing. We all have limited time, and arguing language policy at the IETF is not a good use of time for most of us.  

You could say the same for the documents at the core of many current WGs. 

This is the process we have. If you want to change THAT, it would be a different proposal.

We’re not trying to ban words; we’re trying to help those who might not realize otherwise when certain words have current  connotations they might not have intended.

Joe