Re: why exactly is HRPC for, was Diversity and offensive terminology in RFCs
Ted Lemon <mellon@fugue.com> Fri, 21 September 2018 13:43 UTC
Return-Path: <mellon@fugue.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 26375130DC0 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 06:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 cClVouFPQU_8 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2018 06:43:42 -0700 (PDT)
Received: from mail-it1-x141.google.com (mail-it1-x141.google.com [IPv6:2607:f8b0:4864:20::141]) (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 D568B129385 for <ietf@ietf.org>; Fri, 21 Sep 2018 06:43:41 -0700 (PDT)
Received: by mail-it1-x141.google.com with SMTP id h3-v6so2008542ita.2 for <ietf@ietf.org>; Fri, 21 Sep 2018 06:43:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=glZRL78RlEQMh7LbyiWz2c3tMOLrqjLAVo5mkkxAqIY=; b=Ey+0qFD/EdmaZ7WvR9fzLZdh7i+N8bLxwBwT3OGsv9L272i/6OQajBQ7AT9GcDDbRC H6AaT01WPUYERjzPmKStLXQiOLNU7jU/78Ope2L09xb9i5rLFfTm4IlHZX2aJJ2HOpvK crjE72+pttWxB5JibaMl9E2qZ8O9MX5taEagceXoQUQaYO5wrTrT0HjcPTS8Jhv9FR14 KwRvv5z9C1dNNQzECDCr2NZKsMx7vVuKm/9MVRX/SUlg+12p1hvRvK1WNZ7/l+E53HnU CP0MQlgGAWPkDmG/guXetQo8tfMcV0scU27rO8YfgTnc3Rq77fnG346UpO86vv/YfVUJ fB9Q==
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=glZRL78RlEQMh7LbyiWz2c3tMOLrqjLAVo5mkkxAqIY=; b=GmoLeHlc7ipFi2nulqjjJq2LPuuFu1sOQTuckEX+DPpWdmTD2qY0tscfTgyPoySc1d 1AIdmfYBfg2RAiI0AFdsQA55pyazHn3sgwoogXhn97NIH0QXw1YIfKV2oZ3kB27I/o9/ c0leW/QJJa6VTjCuiTNvZpHl268OH16U1OzkUx2IvCOQRUFSIN9vqzm+A0umXksTmkK6 nYfvwxcSkDV2yLXUNA8zQFn5oUbGYeSyhWLYQvS6kWrQakIfCbmWV5vQF+1mcRFa3j63 VozUQzN1ygS8lugDrdwlKKjlRAlz7oCqbR4b1ytyfafinf4wuBJeVYU6MVKLJi6r9ycs 46Kw==
X-Gm-Message-State: ABuFfojUJDzKqsUwHQX8Y08eNj0+s411wBUg9L2c9la3bPv4XD5Xev6c YS4M/zR2a7FRfFxRKqvUVoC4/4OKgGIqeAKgr21b8zvQJHI=
X-Google-Smtp-Source: ACcGV62umggc4aPR6MOVtuGFFlX4+lTekBx4cAL7eUrEn99zS4pMeXmgBBer8m4WWxRLh1BWhtYhphsr2u3os+hLJc4=
X-Received: by 2002:a24:5f92:: with SMTP id r140-v6mr1965075itb.95.1537537420967; Fri, 21 Sep 2018 06:43:40 -0700 (PDT)
MIME-Version: 1.0
References: <20180920233440.238CA20051DDE5@ary.qy> <5d3da769-5243-f6ee-35b2-d63f9e43b33a@cisco.com>
In-Reply-To: <5d3da769-5243-f6ee-35b2-d63f9e43b33a@cisco.com>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 21 Sep 2018 09:43:29 -0400
Message-ID: <CAPt1N1kJzT0zMmjZA_iKdSE1cJb5t2vvTu5kspnQv2Vi9YpXyA@mail.gmail.com>
Subject: Re: why exactly is HRPC for, was Diversity and offensive terminology in RFCs
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ce59e8057661d353"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zCwFpubwjv-fE0SnhPnTVIl_4eE>
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: Fri, 21 Sep 2018 13:43:45 -0000
Eliot, actually the HRPC RG does attract subject matter experts who speak at HRPC sessions and provide useful input. I’ve gotten some real benefit from these presenters. I do wish they would participate in the process. The master/slave thing was approached as many workplace harassment incidents are: with confidential complaints. This was a real problem that was taken appropriately seriously, and I think the various communities that responded did so appropriately. Your characterization of the situation is unfortunate. Of course it’s also understandable, because this led to the question of whether we should look at other terminology to see if it has the same problem, with zero data to back up such a quest. I agree that that is a fool’s errand. The reason we are having this particular flame war has a lot to do with the lack of crispness of the question that was asked of the IETF, and not much to do with the qualifications of the participants in the RG. On Fri, Sep 21, 2018 at 5:12 AM Eliot Lear <lear=40cisco.com@dmarc.ietf.org> wrote: > Hi John, > > I strongly agree, and would go further. > > As I see it, the HRPC suffers fundamental problems from both participation > and its charter. > > The charter itself, in my opinion, displays a facile understanding of > human rights. It includes the statement: > > * To expose the relation between protocols and human rights, with a focus > on > the rights to freedom of expression and freedom of assembly. > > That belies the need to balance rights contained in frameworks such as the > UDHR, as you and others including myself have repeatedly noted. We have > largely been ignored. The poor interdisciplinary composition of the group > as well as its sole output reflects this regrettable constraint. > > In this latest debacle, a position was put forth that is largely > unsubstantiated. The only research I as a layperson have found finds that > harm related to offensive language is contextually determined.[1] Surely > it's the case that a choice of words *can* harm, and maybe even harm > human rights. However, the HRPC appears to not have the expertise either in > psychology or linguistics to even have a serious discussion about language, > and the co-chair has attempted to stifle debate. The research group is not > having a discussion that reflects the results or ongoing work of any > research. > > As you say, there really are serious human rights issues relating to our > technology that we as a community could and should address. Unfortunately, > so far as I can tell, there are no criminologists, members from the law > enforcement community, or human rights experts from interested > governments. While it's always difficult to engage interdisciplinary > experts in the HRPC, the sole focus on a subset of human rights clearly > presents an additional obstacle. Research *is* happening, but it is > happening elsewhere and with zero collaboration/coordination from HRPC.[2] > > If this entire debate over master/slave is about inclusiveness, nothing > could harm that objective more than advocacy of particular political > positions. Sadly, that is precisely what focusing on a small subset of > rights has led to. The HRPC should either be rechartered or closed. > Because I am skeptical we can really attract the right participants, *I > lean toward closure*. > > Eliot > > [1] Jay, T. (2009). Do offensive words harm people? Psychology, Public > Policy, and Law, 15(2), 81-101. > http://dx.doi.org/10.1037/a0015646 > [2] Savage, C., "Justice Dept. Revives Push to Mandate a Way to Unlock > Phones", The New York Times, 24 Mar 2018, > https://www.nytimes.com/2018/03/24/us/politics/unlock-phones-encryption.html > > > On 21.09.18 01:34, John Levine wrote: > > In article <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> <cafa1282-ae6a-93de-ea4a-d100af28d8b8@digitaldissidents.org> you write: > > 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. > > If this is really the best that HRPC can do, I would suggest that it's > time for the IRTF to consider whether to shut it down. > > When I've gone to HRPC sessions, I have heard endless papers about > more or less plausible threats to freedom of expression or to > anonymous speech (which is not the same thing.) More than once I have > stood up at HRPC sessions and noted that the Universal Declaration of > Human Rights has thirty articles, and none of the discussion deals > with more than two of them. The chairs have assured me that they are > equally interested in the other rights, but the evidence of that is > pretty thin. > > What about article 12, protection agaisnt attacks on honor and > repuation? What is HRPC doing about trolling and other online > attacks? > > Or article 17, nobody shall be arbitrariy deprived of his property? > What is HRPC doing to keep our protocols from being used to enable > phishing and other online theft? > > Or article 23, the right to rest and leisure? What is HRPC doing to > keep our protocols from being used to put people on a 24 hour > electronic leash? > > Instead, we get this stuff. Even if you think that the language in > our RFCs is problematic, which for the most part I don't, I am > confident that no RFC has ever enslaved anyone, nor put anyone on a > secret list that kept them from working (the actual meaning of > blacklist for people who know their history.) > > There are real human rights problems that HRPC could engage with, but > don't. They need to make up their mind whether they're serious. > > R's, > John > > > > >
- 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