Re: Diversity and offensive terminology in RFCs

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Thu, 20 September 2018 13:34 UTC

Return-Path: <kathleen.moriarty.ietf@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 D8713129C6B for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 06:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 VTIjxwyU4Pl0 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 06:34:43 -0700 (PDT)
Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::241]) (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 07453130DE8 for <ietf@ietf.org>; Thu, 20 Sep 2018 06:34:43 -0700 (PDT)
Received: by mail-oi0-x241.google.com with SMTP id y207-v6so8332881oie.13 for <ietf@ietf.org>; Thu, 20 Sep 2018 06:34:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=R5qLmvHDPD0PE5zvbZeQ4c+/w49lL+0VOZmJ1X+bfJc=; b=TebAKV6buAnLLvofTDiLD3J4hPVBsADKKtxRPel4H5XPHM2LP20NDwSfnTLmkd94nf 2o0sjaUYgzA0bQKR0dpul9NLHaAyMHFdUFteoUBMJE2QpP25DTvM1pB/5Ig4UDHdTgoW 7sBejVhmT2oJjrtXuaPv9vn54gzX7Gzk7N/XVpDB1BPFkL128xWpqd+/1ABlvkSseYJ8 KrR/MNL+1nh8xcsy+S8vRzyiWSWWGXP5wKGG7KajAgIbbkTWsLZV+B0togBxQulemEaq YIw6l5uIsVs00rTQAwzGSgfV1Dz0McJVsmTjSwH6FteUEmVwixGWTbggjW/Ubic9nIt4 bLCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=R5qLmvHDPD0PE5zvbZeQ4c+/w49lL+0VOZmJ1X+bfJc=; b=Q9Rfk3p5TsZDJJ5/N4wYjrFbUYuq9Sf2c5jWbnUx6UKJy9ZRHHMbWFcot4h4QzULaY LOrRG0QCMVsoTGIjYpxOHhO31+65SC2bubw3I5fBZtP5QQwnpMo55IB3FZaW+3WkChae PNLSe7p1Zvb72sW1TpRcwaXuEQP/z43SM31O+r32M5/WSRAGFVwVBlK/2cEPY65UT2ob CPdPGJek6v5XbQhvlTbIbluD2hYhv6w6TqvBItwdONSjFZ/4ZFfE1xHdcbIrsLwBIKgN 83YzwT8nKDPVomfHM9OTzi5qddl+7IWaZsLQOkf6gMYGdEnYsNQ9EIAoZ69FuBNIGV+X kzMw==
X-Gm-Message-State: APzg51BTABdHmsl9LpeGeohR0t2ED81oOXt5YdbS8rv+dW1fXMpLnC4m /xmxiiKExzKcW1RDOWCimcCE/kz/wLkBncmg29MfYg==
X-Google-Smtp-Source: ANB0Vdad7G5Lz5vY9lF4dGBcBA5e5yQHjhHu/A5t3KcBjpxjPmWWE9DN0XNQwM6JyiRTkM0DGrYCCfk0CT1SzVgyaA8=
X-Received: by 2002:aca:2318:: with SMTP id e24-v6mr1638754oie.262.1537450482250; Thu, 20 Sep 2018 06:34:42 -0700 (PDT)
MIME-Version: 1.0
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <20180920132601.uwv2lblcvr4ojtk5@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <20180920132601.uwv2lblcvr4ojtk5@faui48e.informatik.uni-erlangen.de>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 20 Sep 2018 09:34:05 -0400
Message-ID: <CAHbuEH7jeGLBMH8Yi+_o+o-NvZKmWt4KbtwbP-8XtL0taUCx_Q@mail.gmail.com>
Subject: Re: Diversity and offensive terminology in RFCs
To: tte@cs.fau.de
Cc: Niels ten Oever <lists@digitaldissidents.org>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000daba1705764d957e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0rmcBWMbrZkGjBLlWIKKJhXt62Q>
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 13:34:46 -0000

On Thu, Sep 20, 2018 at 9:26 AM Toerless Eckert <tte@cs.fau.de> wrote:

> I also find the stereotyping of names in signalling terminology highly
> offensive and non-inclusive: https://en.wikipedia.org/wiki/Alice_and_Bob
>
> Why are only Alice and Bob so chatty to always have the most conversations
> ?
> Won't Carol get depressions from always being a third rail ? Will your kids
> ever get jobs if you name them Craig, Mallory, Eve or Heidi ?  And so on.
> These SIP heads are ruining the life of our kids!
>

And what if your last name were Moriarty?  You'd never have the community
be okay with you as a Security AD? ;-)

I'm fine with Block/permit lists, but don't think there is a racial
connotation to black/white list.  White lists being preferred may be where
the issue arrises I'm guessing.  Switching would be fine with me.

I already say active interception or session hijacking and think that's a
fine replacement for man-in-the-middle.  I didn't see an issue with
man-in-the-middle.

I do recall a recent draft coming through the IESG (within the last year or
so) with monkey-in-the-middle and remember doing some searches on it prior
ro entering comments on the draft.  I think it was commented on by an AD,
but don't remember where that landed.

Best regards,
Kathleen

>
> *sigh*
>
> Keep your virtue signalling out of my language!
>
> --
> Toerless
>
> On Thu, Sep 20, 2018 at 11:25:58AM +0200, Niels ten Oever wrote:
> > Hi all,
> >
> > On the hrpc-list [0] there has been an intense conversation which was
> > spurred by the news that the Python community removed Master/Slave
> > terminology from its programming language [1].
> >
> > In the discussion that followed it was remarked that in RFCs terms like
> > Master/Slave, blacklist/whitelist, man-in-middle, and other terminology
> > that is offensive to some people and groups is quite common.
> >
> > This is not a discussion that can be resolved in hrpc, but rather should
> > be dealt with in the IETF community (because hrpc doesn't make policy
> > for terminology in the IETF), which is why I am posting this here.
> >
> > If people find the discussion worthwhile, we might also be just in time
> > to request a BoF on this topic.
> >
> > Looking forward to discuss.
> >
> > Best,
> >
> > Niels
> >
> >
> > [0] https://mailarchive.ietf.org/arch/browse/hrpc/
> > [1]
> >
> https://motherboard.vice.com/en_us/article/8x7akv/masterslave-terminology-was-removed-from-python-programming-language
> >
> >
> > --
> > Niels ten Oever
> > Researcher and PhD Candidate
> > Datactive Research Group
> > University of Amsterdam
> >
> > PGP fingerprint          2458 0B70 5C4A FD8A 9488
> >                    643A 0ED8 3F3A 468A C8B3
>
>

-- 

Best regards,
Kathleen