Re: IESG Statement On Oppressive or Exclusionary Language

Nico Williams <nico@cryptonector.com> Sun, 09 August 2020 17:52 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 555AD3A0805 for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 10:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_MSPIKE_H2=-0.001, 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 n--zXERZpl_6 for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 10:52:21 -0700 (PDT)
Received: from chocolate.birch.relay.mailchannels.net (chocolate.birch.relay.mailchannels.net [23.83.209.35]) (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 14B5B3A0828 for <ietf@ietf.org>; Sun, 9 Aug 2020 10:52:20 -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 2530B360CBA; Sun, 9 Aug 2020 17:52:20 +0000 (UTC)
Received: from pdx1-sub0-mail-a76.g.dreamhost.com (100-96-5-127.trex.outbound.svc.cluster.local [100.96.5.127]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id A734C360C84; Sun, 9 Aug 2020 17:52:19 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a76.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.8); Sun, 09 Aug 2020 17:52:20 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Exultant-Befitting: 3317dfac5059abb7_1596995539947_1996376643
X-MC-Loop-Signature: 1596995539947:402571603
X-MC-Ingress-Time: 1596995539947
Received: from pdx1-sub0-mail-a76.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a76.g.dreamhost.com (Postfix) with ESMTP id 67D28B2362; Sun, 9 Aug 2020 10:52:19 -0700 (PDT)
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:content-transfer-encoding; s= cryptonector.com; bh=6BAcHRhto/qKcUE50kDV3mwY4Kw=; b=IGdYcDL3+X8 PB5BeGZ4Q8ksTy+r3hUgtUQ7qU3+OfHOrfWZPB1fv4xu8s6dfFLnC2mkeGIMr9FE he/ECKS+KK9GDXFOxiyWeaMncsMouhGDD+ncArGZpEEmdlV4jwexfT6GrYhlfk7o 4y2WKwvTQV6JedlEJcUdpTj1A4j/t/UM=
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-a76.g.dreamhost.com (Postfix) with ESMTPSA id 6E5BDB235D; Sun, 9 Aug 2020 10:52:17 -0700 (PDT)
Date: Sun, 09 Aug 2020 12:52:15 -0500
X-DH-BACKEND: pdx1-sub0-mail-a76
From: Nico Williams <nico@cryptonector.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: Lloyd Wood <lloyd.wood=40yahoo.co.uk@dmarc.ietf.org>, Nadim Kobeissi <nadim@symbolic.software>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
Message-ID: <20200809175214.GA3100@localhost>
References: <60160A936BE682CEDE0704E1@PSB> <20200809053037.GV3100@localhost> <5c768c35-edb6-0180-737e-fa0c78cb971d@gmail.com> <20200809063805.GX3100@localhost> <005afe55-7c2c-a0a6-e66f-4513e006ab42@gmail.com> <20200809070448.GY3100@localhost> <20200809084341.GW40202@straasha.imrryr.org> <196BA5B1-92B6-4EC4-897E-F5C14E12647D@symbolic.software> <1783494857.1475756.1596964788830@mail.yahoo.com> <76FAC452-8C73-498E-920E-4A7E9D4A4E00@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <76FAC452-8C73-498E-920E-4A7E9D4A4E00@akamai.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduiedrkeeigdduudeiucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtugfgjggfsehtkeertddtreejnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecuggftrfgrthhtvghrnhepgedviedvgefgtdfhtefghfeuffeglefggefhvdfgtdffhfevffeiheffieeuudefnecukfhppedvgedrvdekrddutdekrddukeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomh
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nSPrx7yr3lsfnsMXFrsJVdGOh1c>
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, 09 Aug 2020 17:52:33 -0000

On Sun, Aug 09, 2020 at 03:39:33PM +0000, Salz, Rich wrote:
> We are not talking about board games here.  Let’s stay focused and not
> go to reduction ad absurdum arguments. We are talking about the
> language used in IETF RFC’s.

Viktor's explanation of how "master" in contexts w/o "slave" can't be
offesnive needs to be addressed.  Really, asserting that "master secret"
is problematic is simply credibility-destroying.