Re: Diversity and offensive terminology in RFCs
Ole Troan <otroan@employees.org> Thu, 20 September 2018 12:25 UTC
Return-Path: <otroan@employees.org>
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 DD8DD130E9A for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 05:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 xIZET2zrrD7U for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 05:25:04 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E23B3130DE2 for <ietf@ietf.org>; Thu, 20 Sep 2018 05:25:04 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 88CA2FECBBF9; Thu, 20 Sep 2018 12:25:03 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 7CE9963F8E6; Thu, 20 Sep 2018 14:25:01 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Diversity and offensive terminology in RFCs
From: Ole Troan <otroan@employees.org>
In-Reply-To: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org>
Date: Thu, 20 Sep 2018 14:25:01 +0200
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E80AD68-642D-4424-9B30-D19B6411B7AF@employees.org>
References: <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org>
To: Niels ten Oever <lists@digitaldissidents.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j39eo-wdmkvj1ix_k-Sv8t9RMrs>
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 12:25:07 -0000
There is one word used a lot in the IETF that I find terribly offensive though. IPv4. Can we get rid of that? O. > On 20 Sep 2018, at 11:25, Niels ten Oever <lists@digitaldissidents.org> 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 >
- Diversity and offensive terminology in RFCs Niels ten Oever
- Re: Diversity and offensive terminology in RFCs Riccardo Bernardini
- Re: Diversity and offensive terminology in RFCs Stewart Bryant
- Re: Diversity and offensive terminology in RFCs Petr Špaček
- Re: Diversity and offensive terminology in RFCs Niels ten Oever
- Re: Diversity and offensive terminology in RFCs Dave Cridland
- Re: Diversity and offensive terminology in RFCs Loa Andersson
- Re: Diversity and offensive terminology in RFCs Mukund Sivaraman
- SV: Diversity and offensive terminology in RFCs Anne-Marie Eklund-Löwinder
- RE: Diversity and offensive terminology in RFCs Roberta Maglione (robmgl)
- Re: Diversity and offensive terminology in RFCs Ole Troan
- Re: Diversity and offensive terminology in RFCs Michal Krsek
- Re: Diversity and offensive terminology in RFCs Tony Finch
- Re: Diversity and offensive terminology in RFCs Job Snijders
- Re: Diversity and offensive terminology in RFCs Anton Ivanov
- Re: Diversity and offensive terminology in RFCs Anton Ivanov
- RE: Diversity and offensive terminology in RFCs Adrian Farrel
- Re: SV: Diversity and offensive terminology in RF… Jaap Akkerhuis
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Andrew Sullivan
- Re: Diversity and offensive terminology in RFCs Kathleen Moriarty
- Re: Diversity and offensive terminology in RFCs lloyd.wood
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: SV: Diversity and offensive terminology in RF… lloyd.wood
- Re: Diversity and offensive terminology in RFCs Paul Wouters
- Re: Diversity and offensive terminology in RFCs Paul Wouters
- Re: Diversity and offensive terminology in RFCs lloyd.wood
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Stephan Wenger
- Re: Diversity and offensive terminology in RFCs Mark Nottingham
- Re: Diversity and offensive terminology in RFCs Stephen Farrell
- RE: Diversity and offensive terminology in RFCs John E Drake
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Dick Franks
- Re: Diversity and offensive terminology in RFCs ned+ietf
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Paul Hoffman
- Re: SV: Diversity and offensive terminology in RF… Evan Hunt
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- ""Man-in-the-middle""? <was, Re: SV: Diversity an… Charlie Perkins
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: Diversity and offensive terminology in RFCs Melinda Shore
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: SV: Diversity and offensive terminology in RF… Michael StJohns
- Re: ""Man-in-the-middle""? <was, Re: SV: Diversit… Dave Aronson
- Re: SV: Diversity and offensive terminology in RF… Heather Flanagan
- Re: Diversity and offensive terminology in RFCs Mark Nottingham
- Re: Diversity and offensive terminology in RFCs Heather Flanagan
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Evan Hunt
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs John C Klensin
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: SV: Diversity and offensive terminology in RF… Anton Ivanov
- Re: Diversity and offensive terminology in RFCs Yoav Nir
- Re: Diversity and offensive terminology in RFCs Kyle Rose
- Re: Diversity and offensive terminology in RFCs Brian E Carpenter
- Re: Diversity and offensive terminology in RFCs Carsten Bormann
- Re: Diversity and offensive terminology in RFCs Dave Cridland
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: why exactly is HRPC for, was Diversity and of… John Levine
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: Diversity and offensive terminology in RFCs Brian E Carpenter
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: why exactly is HRPC for, was Diversity and of… Mark Rousell
- Re: why exactly is HRPC for, was Diversity and of… Melinda Shore
- Re: Diversity and offensive terminology in RFCs Alia Atlas
- Re: why exactly is HRPC for, was Diversity and of… Allison Mankin
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: Diversity and offensive terminology in RFCs Mark Rousell
- Re: Diversity and offensive terminology in RFCs Phillip Hallam-Baker
- Re: Diversity and offensive terminology in RFCs Lloyd Wood
- Re: Diversity and offensive terminology in RFCs Lloyd Wood
- On-path attackers (Was: Re: Diversity and offensi… Jari Arkko
- Re: why exactly is HRPC for, was Diversity and of… Eliot Lear
- Re: why exactly is HRPC for, was Diversity and of… Niels ten Oever
- Re: why exactly is HRPC for, was Diversity and of… Lloyd Wood
- Re: Diversity and offensive terminology in RFCs Eliot Lear
- Re: On-path attackers (Was: Re: Diversity and off… Kathleen Moriarty
- Re: Diversity and offensive terminology in RFCs Alissa Cooper
- Re: why exactly is HRPC for, was Diversity and of… Paul Wouters
- Re: why exactly is HRPC for, was Diversity and of… Ted Lemon
- Re: On-path attackers (Was: Re: Diversity and off… Donald Eastlake
- Re: why exactly is HRPC for, was Diversity and of… Lloyd Wood
- Re: Diversity and offensive terminology in RFCs Niels ten Oever
- Re: On-path attackers (Was: Re: Diversity and off… Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Ted Lemon
- Re: Diversity and offensive terminology in RFCs Anton Ivanov
- Re: On-path attackers (Was: Re: Diversity and off… Ted Lemon
- Re: why exactly is HRPC for, was Diversity and of… John R Levine
- Re: Diversity and offensive terminology in RFCs Paul Wouters
- Re: Diversity and offensive terminology in RFCs Eliot Lear
- Re: Diversity and offensive terminology in RFCs Phillip Hallam-Baker
- Re: Diversity and offensive terminology in RFCs Toerless Eckert
- Re: Diversity and offensive terminology in RFCs Nico Williams
- Re: why exactly is HRPC for, was Diversity and of… Avri
- Re: Diversity and offensive terminology in RFCs Spencer Dawkins at IETF
- Re: Diversity and offensive terminology in RFCs Dave Cridland
- Re: why exactly is HRPC for, was Diversity and of… John Levine
- Re: why exactly is HRPC for, was Diversity and of… Spencer Dawkins at IETF
- Re: why exactly is HRPC for, was Diversity and of… Allison Mankin
- Tell me if I should send this Re: why exactly is … Mallory Knodel
- Mallory-in-the-middle attacks (Re: SV: Diversity … Nico Williams
- Re: Diversity and offensive terminology in RFCs Nico Williams
- Re: On-path attackers (Was: Re: Diversity and off… Brian E Carpenter
- Re: Diversity and offensive terminology in RFCs Glenn Deen
- Re: Mallory-in-the-middle attacks (Re: SV: Divers… Nico Williams
- Re: Tell me if I should send this Re: why exactly… lloyd.wood
- Re: Mallory-in-the-middle attacks (Re: SV: Divers… Mallory Knodel
- Re: why exactly is HRPC for, was Diversity and of… Mallory Knodel
- Re: Diversity and offensive terminology in RFCs Abdussalam Baryun
- Re: why exactly is HRPC for, was Diversity and of… S Moonesamy
- Re: why exactly is HRPC for, was Diversity and of… Mallory Knodel