Re: A contribution to ongoing terminology work
Nico Williams <nico@cryptonector.com> Sun, 04 April 2021 20:16 UTC
Return-Path: <nico@cryptonector.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 D59463A18AC for <ietf@ietfa.amsl.com>; Sun, 4 Apr 2021 13:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level:
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 eKhaGwpczkWi for <ietf@ietfa.amsl.com>; Sun, 4 Apr 2021 13:16:51 -0700 (PDT)
Received: from gainsboro.ash.relay.mailchannels.net (gainsboro.ash.relay.mailchannels.net [23.83.222.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 479C93A18A6 for <ietf@ietf.org>; Sun, 4 Apr 2021 13:16:49 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 083936419CC; Sun, 4 Apr 2021 20:16:46 +0000 (UTC)
Received: from pdx1-sub0-mail-a70.g.dreamhost.com (100-105-161-106.trex.outbound.svc.cluster.local [100.105.161.106]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 8892D641859; Sun, 4 Apr 2021 20:16:45 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a70.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.105.161.106 (trex/6.1.1); Sun, 04 Apr 2021 20:16:45 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Snatch-Macabre: 2031a18b70bca9d7_1617567405875_1993288675
X-MC-Loop-Signature: 1617567405875:1448125628
X-MC-Ingress-Time: 1617567405875
Received: from pdx1-sub0-mail-a70.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a70.g.dreamhost.com (Postfix) with ESMTP id 4593E85DB1; Sun, 4 Apr 2021 20:16:45 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=7l1/3mVL9EFktV vkwgt2ueW1Geg=; b=FbsmocFjd3CHFw4qJb1kc2f2oPRX+p6NpWPjK5/BngYoHU /h+/a2QoTk/jPdnsEX5001+2oEtjH1NtHX4CLCf4qtGIE7HkCEhKmdRoXMWCbhTB IM0O5PZWQqzKax+WFgkRNyvp0Rnx0+fONQLujUTkH8+eqmVG5OWFeMYLGqBDU=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a70.g.dreamhost.com (Postfix) with ESMTPSA id 37DF87FF82; Sun, 4 Apr 2021 20:16:43 +0000 (UTC)
Date: Sun, 04 Apr 2021 15:16:41 -0500
X-DH-BACKEND: pdx1-sub0-mail-a70
From: Nico Williams <nico@cryptonector.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Subject: Re: A contribution to ongoing terminology work
Message-ID: <20210404201640.GD3828@localhost>
References: <1e4feea2-2c81-b31a-04e3-d4c9a4adbaf7@lounge.org> <20210402163230.GH79563@kduck.mit.edu> <4c82de79-1e40-2eed-909b-8a288284393d@lounge.org> <439a33c9-5791-4c90-76a3-54aab828a37d@network-heretics.com> <5C955F3B-2EE7-43DD-85BA-DA1C1CF353F1@tzi.org> <7b3ba302-ec36-eb8d-7461-861a0b6651ac@network-heretics.com> <0dca7a0d-d51e-4c67-cc96-a44de0141480@gmail.com> <9c369a34-d47c-3af0-9793-8342f5f6ec63@network-heretics.com> <c613095d-f0b4-8df7-e703-d1b3c52bffc5@gmail.com> <tslpmzctgoi.fsf@suchdamage.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <tslpmzctgoi.fsf@suchdamage.org>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U9D34fc_d18CjdUIImeLBUW9yaI>
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: Sun, 04 Apr 2021 20:16:56 -0000
On Fri, Apr 02, 2021 at 07:22:53PM -0400, Sam Hartman wrote: > Now let us come to "A Modest Proposal." > This is not the first time that satirical essay has come up in the IETF > context. > Ted Hardie used it a couple of times I can remember, and I don't think > he was the first in my history in the IETF. > And yet several of those times, specific people in our community spoke > up and said that because of their background, they felt excluded, hurt, > or offended by that particular reference. > > So, we as a community have history. We know that essay strikes at > people because of their racial or other aspects of their background. > > USING THAT REFERENCE WITHOUT TAKING THAT INTO ACCOUNT IS DISRESPECTFUL > and EXCLUSIONARY TOWARD CURRENT CONTRIBUTORS. Let's start with the offensiveness of Swift's "A Modest Proposal". I read it yesterday. It is extremely offensive. It must have been extremely offensive in 1729. Swift clearly meant it to be so. I won't quote any of the offensive bits of it. If we stop there, then we must thoroughly condemn Swift and -who knows- maybe find new terms for "litte-endian" and "big-endian" and issue new versions of RFCs that have those terms. But Swift deployed this offensive satire for a noble cause: to shame the UK into treating Ireland and Irish people and the poor better. Swift obviously did not hold any beliefs like what are contained in that essay -- quite the contrary. It is because of that noble cause that we tolerate the offensivness of that essay. Now let's talk about shared history. I myself had never heard of past controversies at IETF to do with A Modest Proposal, and I've been a participant here for twenty years. Perhaps Lloyd had not either. It would be exclusionary in the extreme to demand that one search or even read decades' worth of IETF mailing list archives before participating, or even just before posting satire. > If you're going to make a "modest proposal," you'd better be explaining > why you chose to do something that is hurtful. "A Modest Proposal" can be quite hurtful if we ignore that it is satire and its noble cause. It's much harder to accept that it's hurtful if one accepts that it is satire for a noble cause -- not that can't be hurtful, but that we need a fairly high bar for that, else we might be flooded with grievances. > What other options did you consider? Why could you not make your point > that way? I posted separately about the context. I can't speak for Lloyd, but I suspect that he must have felt it was time to reach for satire given that context. As wikipedia notes, use of "A Modest Proposal" is something of a trope in English writing: | This satirical hyperbole mocked heartless attitudes towards the poor, | as well as British policy toward the Irish in general. | | In English writing, the phrase "a modest proposal" is now | conventionally an allusion to this style of straight-faced satire. Nico --
- A contribution to ongoing terminology work lloyd.wood@yahoo.co.uk
- Re: A contribution to ongoing terminology work Lars Eggert
- Re: [Terminology] A contribution to ongoing termi… Mallory Knodel
- Re: A contribution to ongoing terminology work Vittorio Bertola
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Benjamin Kaduk
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Masataka Ohta
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Nick Hilliard
- Re: A contribution to ongoing terminology work Behcet Sarikaya
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Benjamin Kaduk
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Marc Petit-Huguenin
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Keith Moore
- RE: A contribution to ongoing terminology work Larry Masinter
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work S Moonesamy
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Sam Hartman
- RE: A contribution to ongoing terminology work Larry Masinter
- Re: A contribution to ongoing terminology work Sam Hartman
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Vittorio Bertola
- Re: A contribution to ongoing terminology work Masataka Ohta
- Re: A contribution to ongoing terminology work Masataka Ohta
- Re: A contribution to ongoing terminology work Masataka Ohta
- April 1st RFCs (was Re: A contribution to ongoing… Adam Roach
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Randy Presuhn
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work lloyd.wood@yahoo.co.uk
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Nick Hilliard
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Joel M. Halpern
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work S Moonesamy
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Leif Johansson
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Wes Hardaker
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker
- Re: A contribution to ongoing terminology work Lloyd W
- Re: A contribution to ongoing terminology work Fernando Gont
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Lloyd W
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker