Re: [Gendispatch] draft charter text: terminology-related WG

Fernando Gont <fgont@si6networks.com> Mon, 15 February 2021 21:25 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F1293A1193 for <gendispatch@ietfa.amsl.com>; Mon, 15 Feb 2021 13:25:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Su16tSztYDD0 for <gendispatch@ietfa.amsl.com>; Mon, 15 Feb 2021 13:25:56 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD1453A1190 for <gendispatch@ietf.org>; Mon, 15 Feb 2021 13:25:54 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:1c77:acfc:e6a8:1311] (unknown [IPv6:2800:810:464:2b9:1c77:acfc:e6a8:1311]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 9EC2628027D; Mon, 15 Feb 2021 21:25:50 +0000 (UTC)
To: Bob Hinden <bob.hinden@gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, gendispatch@ietf.org
References: <A531C377-33A4-4138-BE28-788FF5FE267E@sn3rd.com> <CABcZeBPxQrzQZZ2ec+cvpovdkJaXcQ4f8Ged7Om1QPg7UrZ_Ew@mail.gmail.com> <C7451272-56CF-49C7-ABAA-7B8849AAE8DB@cisco.com> <31dc343f-8e73-6afd-1fca-c68fb5b47bd0@lounge.org> <fabe2570-d138-8f35-f14a-a564a00ea7ba@gont.com.ar> <c425e778-429f-eedb-b730-8b6f03dfaa0d@lounge.org> <8a9633db-ecd3-7ec7-e2a6-77088e68b184@huitema.net> <C6606DCF-768C-42A3-AF9B-6547A9A0FD04@gmail.com> <b3645c65-f2d5-cf86-433b-c3270d375314@si6networks.com> <DB0667FF-0FAE-4066-BA22-EDEC29267FC8@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <400022e5-ced5-37e0-2765-81ceb6def69c@si6networks.com>
Date: Mon, 15 Feb 2021 18:17:37 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <DB0667FF-0FAE-4066-BA22-EDEC29267FC8@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/J6z4gqARNu6abItu8UOImMXPNek>
Subject: Re: [Gendispatch] draft charter text: terminology-related WG
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2021 21:25:59 -0000

On 15/2/21 14:23, Bob Hinden wrote:
> Fernando,
> 
>> On Feb 14, 2021, at 12:40 PM, Fernando Gont <fgont@si6networks.com> wrote:
>>
>> On 14/2/21 14:46, Bob Hinden wrote:
>> [...]
>>> I agree.
>>> I also think that diversity in the IETF and language in RFCs are mostly different topics.
>>> Diversity in the IETF is about who participates in the IETF, increasing participation in the IETF, etc.    RFCs are used by a much broader Internet community that the folks who participate in the IETF.
>>
>>
>> Focusing on this, while ignoring the rest, reads a lot like "let's be nice in our documents while we keep people excluded from participating" to me.
> 
> No, not at all.    I think I was clear to say they are different topics.  I did not say anything like you suggested, that is:
> 
>    "let's be nice in our documents while we keep people excluded from participating"

Just for clarification: I didn't mean that *you* (or, for instance, 
anybody) were implying that.

What I meant is that if the issue of language is associated with 
improving inclusiveness, and there's no comprehensive approach to try to 
tackle the problem, it comes across like that.

As suggested by others, one possible way out is to remove any references 
to inclusiveness and diversity when pursuing such work, and simply 
pursue it as "tackling possibly-offensive language".

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492