IETF Logo Mail Archive

Re: Diversity and offensive terminology in RFCs

Dick Franks <rwfranks@acm.org> Thu, 20 September 2018 15:10 UTC

Return-Path: <rwfranks@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 4312E130EB5 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 08:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.503
X-Spam-Level:
X-Spam-Status: No, score=-1.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.146, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 HGHpFhRPrXYc for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 08:10:12 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 87092130EAE for <ietf@ietf.org>; Thu, 20 Sep 2018 08:10:09 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id v16-v6so9765616wro.11 for <ietf@ietf.org>; Thu, 20 Sep 2018 08:10:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=lBcXCcPCuS9eLXpZ/7lshXAtCGHRNPVrGElENdP8p04=; b=etkRnwkBVAbdL29hBOBB94LDJDGIfreCc9G/sx1D36LgH41n+Uz/4DV7CtSelZlCkD LUJ+aOjuCnGdJF3+UPODb2hJF7YnwprnRFLfWiAWfugOGTBDkUaVHzc3WQawJnPHUSex FPrU8eLOuaYO0YOMYG1Haat4AU/qVqFNOio5Dps821r9OEqtxTwBy6WUltJmVye7AyN2 uQFZ547Psp0nta3H8gUXBZpXG5L2xfhOwA1iyf2PRYyA/myWaOoP063WYkhvwR8wxpWu SrcPiJoIBKq1iftuLWsjvdma829+GeHJSObfoRSZapd9TNGXQKITURfJEWdl23eQVxuu El4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=lBcXCcPCuS9eLXpZ/7lshXAtCGHRNPVrGElENdP8p04=; b=SwKJccmDCmx5hrOMmDzJvCpxe3G18TwTJWwl9X1NazyeW+zytygrYXxAqqtjk/HsEb AE6tS5THuaepu/BGUZTDo4p3QZ0wfwwp4zULC1TMSMST0FTx8bHoSJLRWp+X3/NzFqdQ 0I4YQqwScKfKPFnT2SG6UCHGgXxrjdvkWDc19UiaY32Kyrj55U4A5QqTjuvlvUUr0hYY DqKc5hB2TAoE33nzCKSyUecoO6NSmsfolZ3g9Cmqi0BLjS6e5eajg0pjYso+1oR/VhxM 8t9J+Vk9c59kRHUCJrpWfdwcI98235tGTvnxRdglYPMmGYiIK4H89DCFCxzzrC+VVIvj 5TwA==
X-Gm-Message-State: APzg51D6mxuqOGbgO5T/GKoA744o3LsYc8S01VPc7VHQMhSMScZ07zMR GbqAvcDAJgIlMRmKyLy0a7sZ29W4ec31Nsj5KCGhVA==
X-Google-Smtp-Source: ANB0VdbPmwEMgNHq8j49dwVO/RjldWhx2J2wvqk0kLNZf1eUmwMePN8dZ/WkCgneKhTPsARbEv998pn/WuVNwxHG5io=
X-Received: by 2002:adf:e1c5:: with SMTP id l5-v6mr34692975wri.36.1537456207464; Thu, 20 Sep 2018 08:10:07 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 2002:adf:ad71:0:0:0:0:0 with HTTP; Thu, 20 Sep 2018 08:09:26 -0700 (PDT)
In-Reply-To: <137564820.4778399.1537453325898@mail.yahoo.com>
References: <137564820.4778399.1537453325898.ref@mail.yahoo.com> <137564820.4778399.1537453325898@mail.yahoo.com>
From: Dick Franks <rwfranks@acm.org>
Date: Thu, 20 Sep 2018 16:09:26 +0100
X-Google-Sender-Auth: mo_Spz7NCCY86B5RcMRb_8rxqUQ
Message-ID: <CAKW6Ri5o3yVf2bGs-Z+PLTo0g45+EtyP=TM2L2T4O2ZFX3yJXA@mail.gmail.com>
Subject: Re: Diversity and offensive terminology in RFCs
To: IETF Discussion Mailing List <ietf@ietf.org>
Cc: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Content-Type: multipart/alternative; boundary="0000000000001a8e4e05764eebe1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cRR37A8NSfVBQaEHT1KIKG3n1s8>
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:10:16 -0000

On 20 September 2018 at 15:22, <lloyd.wood=40yahoo.co.uk@dmarc.ietf.org>
wrote:

> I too am looking forward to this
> list of problematic terms that
> the IETF should have blackballed.
>

Well, blackball will have to go for starters!


vertically challenged debugging information format  (version 6)

gender-neutral documentation pages






>
>
> Lloyd Wood lloyd.wood@yahoo.co.uk
>
> On Friday, September 21, 2018, 00:12, Paul Wouters <paul@nohats.ca> wrote:
>
> On Thu, 20 Sep 2018, lloyd.wood=40yahoo.co.uk@dmarc.ietf.org wrote:
>
>
> > python has absolutely no problem favouring and promoting whitespace,
> which is racist as.
> > whitespace is so important it gets to come first in the queue on the
> line. because it's white.
>
>
> Since I use white text on a black screen, it is misnamed anyway! It's
> blackspace for me!
>
> We should call it blancspace obviously.
>
> I also remember they had excellent coffee at IETF 95 Buenos Aires
> at a place called Negro and it felt like a weird name to me until I
> learned some more Spanish :P
>
>
> Joking aside, Niels does bring a valid point, and it would be nice if we
> got some guidelines for avoiding these existing known words, and prevent
> us from creating new problematic ones.
>
>
>

v2.23.0 | Report a Bug | By Email