Re: Diversity and offensive terminology in RFCs

Melinda Shore <melinda.shore@gmail.com> Thu, 20 September 2018 15:29 UTC

Return-Path: <melinda.shore@gmail.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 AB0B2130EFF for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 08:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 gX24lvxzpMl7 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 08:29:50 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 E86FE130EC5 for <ietf@ietf.org>; Thu, 20 Sep 2018 08:29:49 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id j8-v6so4502134pll.12 for <ietf@ietf.org>; Thu, 20 Sep 2018 08:29:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=eHFzNLdzzowlzOqYGWMF435vHq4lXmvq3CPdXrCiE/0=; b=MyalfPnkMXqpWZ/tte4eFP4I53CgObw4o5vJaQjbDxV27ZRS1c96Y2UHkDkVtJD9M5 M2EofSBl0e6wM/IAtq8L/f5YVC7a55Szy6XO355N8a+Opz/gits7yQFYW7s83WB7fDXv goLYDVdvEvzglquHXJSIj6ymznHxHqfZzq1iOjEEmXxlMScPsDqbdDmvdrz3znTj7pd6 c55u+NcvBn0Hp5aD1kBO5XWvs5FX3OOJG9taDxB2lHooihOSOwQy/sNYfy1zpAdpjIMU pqlyZjLmAqDOL1tRINXFPE9nLudoyEcukGovJaqOIVlkm7LUPlcMxKYMtZ4wmqw0kXKD w5sA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=eHFzNLdzzowlzOqYGWMF435vHq4lXmvq3CPdXrCiE/0=; b=J+kvlLfBId3Y655MukDQZg1bIk14Mqk3d23cXZp3Jn1n7FpYjcg4a+/EYSpvuAw7hE HmcGIKHN22U8Haa15azEdeiRaqCYGgW6flYgcvuntbxy+C6PVkJ887fsUZxmHKrJ8OB6 x1rBWX/I+fAsDO18TEzaN/mmzH6LbvMkG4f8wPSl2XsoiEh0+VjKE2wpFx3eQSIqxJRx sUpbVD0VQQ/xL3kMxOzxMQE3o2veteNVQ9fuLWxehX9bzoaHae/odjgLw016UDHin0Hw ZSmfL6y4s21OFcmObblXDK94JFCPQZGhhWjyCaLgS4JkxlX1BEvwrKLdw4GGfvzodI4J z+nw==
X-Gm-Message-State: APzg51Avuuyu/cbwEKY4b+QJYaIvIs/a0SV5jm+r6+awLaj4mzz4Z4Ad nF7cHYCh9YZuOLgJB3kAO1Bzso6V
X-Google-Smtp-Source: ANB0VdbBkrcLI4G/JfyJX2HWRPCFxAEbr8nqVkMdHsOefEGBcXBY1HrfUkD9SX7np6nH3Z7cvpQExQ==
X-Received: by 2002:a17:902:900a:: with SMTP id a10-v6mr39967120plp.143.1537457389093; Thu, 20 Sep 2018 08:29:49 -0700 (PDT)
Received: from aspen.local ([63.140.88.205]) by smtp.gmail.com with ESMTPSA id b18-v6sm30254301pgk.15.2018.09.20.08.29.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Sep 2018 08:29:48 -0700 (PDT)
Subject: Re: Diversity and offensive terminology in RFCs
To: Toerless Eckert <tte@cs.fau.de>
Cc: ietf@ietf.org
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <20180920132601.uwv2lblcvr4ojtk5@faui48e.informatik.uni-erlangen.de> <CAHbuEH7jeGLBMH8Yi+_o+o-NvZKmWt4KbtwbP-8XtL0taUCx_Q@mail.gmail.com> <20180920143103.lvg6rmkzqfyjq3fr@faui48e.informatik.uni-erlangen.de> <52399791-9285-bcab-4fcd-3eb0f0a1f64f@gmail.com> <20180920151907.5wxxlccrvcgzjzcz@faui48e.informatik.uni-erlangen.de>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <10fdf9dc-f457-4683-8ce2-f0b36f105d83@gmail.com>
Date: Thu, 20 Sep 2018 07:29:46 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20180920151907.5wxxlccrvcgzjzcz@faui48e.informatik.uni-erlangen.de>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YTpsrhmyPKm7esp2zdX_bdvMlck>
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, 20 Sep 2018 15:29:59 -0000

On 9/20/18 7:19 AM, Toerless Eckert wrote:
> virtue signalling describes the condition where a proposed change
> does not address or resolve real concerns but is just introduced
> to suggest empathy and only accelerates the euphemism treadmill. 

Yes, we're familiar with the terminology and how it's used.

Allow me to suggest that telling people their concerns aren't
"real" does not contribute to moving the discussion forward,
but rather the opposite.  What do you expect to *actually* result
from telling people that?  Try gaming this out, see where you
end up.

Melinda