Re: IESG Statement On Oppressive or Exclusionary Language

Yoav Nir <ynir.ietf@gmail.com> Sun, 09 August 2020 22:09 UTC

Return-Path: <ynir.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 74C9D3A0E07 for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 15:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=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 (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 6a_6HfLI2VMp for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 15:09:38 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 0EF453A0E04 for <ietf@ietf.org>; Sun, 9 Aug 2020 15:09:38 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id f7so6456943wrw.1 for <ietf@ietf.org>; Sun, 09 Aug 2020 15:09:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=v8D8GU0i/vR+NjuHWoc/CQmh26ndYU0g6MJ/hz6eXJ4=; b=eKxggcYnaDAaGjfgp6G5fjMnCUWyAIAFhgNRs1iA7QuyYxHEXplbVEzzzG/jT1eWYp +PBXNcKeGqk3zYuCgI2acc275wcm/5U8FOfnY1urZL0ILkQdG0amZCQUvDZaw2dCg1XN YSkD4wtcqdhMoOQR24TB0XVLcunSJGQFhFbYL0XJ2R5RbC+9kmNjGg8+u78fUrWyrcIs ZXLezirxU+M6MAr+qZbs56bVUadCAVILMg2y6xQwxcaT1dsAQ2oDyPUHbRUYv0YaL+BI pIERkPgLIob8Re5ohHR1tGezfKWOjCNnCiutoiEv/1YdEmz8WqpDVgJQrgCOnw2lzIn8 VpyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=v8D8GU0i/vR+NjuHWoc/CQmh26ndYU0g6MJ/hz6eXJ4=; b=VSjTG/UVI/QVh4W3MRUh0KuatigTHXWOEICXnuMSDQBCw8dms2rvR17pg/pjtIqoXL U5x10SkN0JLFZZqQe2oldjMn36iXpcUhx0s06JJ7TdEwNtiJi2IlSn4f6PdTUdzVPOzZ uZzLYvUuWsn7fsQcewFzz8Sdrg5onTwaxZikaPkuXxm4aOOgvh2O8kasUqlZSYYZCIRy Mj4kw4y6mqjdcXCeFMiTd4z46fLOYFhJWYM/d3mKVcHkkhtt51gQrEapphPBCV5VkjFR 9VOP8nkXHIlG+O+y+7CbiUsx5tV/CQikPld4+PJYqtwAg7VeMfsQ3nZlDX1iReAxfQJr ynmw==
X-Gm-Message-State: AOAM531kp7e2ZR9OjsmwFaXNGZUMF0/mGkvt10+0mU+HXbX8/rondr1t nbriKMJBQDV++cUHQ65K7wY2LORC
X-Google-Smtp-Source: ABdhPJwtHzel+9+i7HOusbzNCzjGvnF79FymqU9BaGevehZE4F7w2OjCv5+BgzJk7OOoZliSvH3D0A==
X-Received: by 2002:adf:9ed1:: with SMTP id b17mr21046666wrf.140.1597010976374; Sun, 09 Aug 2020 15:09:36 -0700 (PDT)
Received: from [192.168.1.17] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id s20sm18157294wmh.21.2020.08.09.15.09.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Aug 2020 15:09:35 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <ab2c95a9-3974-23da-e289-b84321f0d8b4@joelhalpern.com>
Date: Mon, 10 Aug 2020 01:09:33 +0300
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <37A9381E-39A3-47FB-AE3C-542998AF0790@gmail.com>
References: <20200809175214.GA3100@localhost> <DEC952F4-379C-4C97-8772-DA6C556A3AF1@strayalpha.com> <5d3052b7-b95b-0c62-1757-306560a30348@acm.org> <E1C0BBFF-0BC2-4D46-8817-E82BD2186042@gmail.com> <ab2c95a9-3974-23da-e289-b84321f0d8b4@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oD8IzU_8b7WKnAh3fgZu0VG0QAs>
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 22:09:40 -0000

It doesn’t matter if you or anyone else thinks this is an odd idiom.  It is an idiom that has been used for centuries.  Its use in cryptography borrows from that use as does the word “key” itself. They both help understanding in that they reference common idioms. To replace them with made up names requires significant justification, where none has been given in this thread.



> On 10 Aug 2020, at 0:25, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> Chess Master, as with Master of Arts, and Masterpiece, ... is a usage of "master" indicating one who posses a very high degree of skill.
> 
> While I do not know what others expect, I do not expect those usages to change.  Words have many meanings.
> 
> The usage of "master" meaning "the one in charge" has, over time, become contaminated with historical usage of a more specific kind of charge. While there are usage that may be reasonable to retain (outside of IETF purview), it seems to me that we should be looking at the places we use that term and see whether it is a good choice.
> While "Master key" is outside of the IETF purview, it is actually a very odd idiom.  "Master secret", which is in our purview, is similarly an odd usage that does not do a good job of conveying our meaning.
> 
> We often end up with sloppy terms.  We often just live with them.  Even though it makes it harder for folks to understand our work.  In this case, we are being asked to look for better terms because the historically chosen terms have bagggage we distinctly did not intent.
> 
> Yours,
> Joel
> 
> On 8/9/2020 5:06 PM, Yoav Nir wrote:
>>> On 9 Aug 2020, at 22:56, Marc Petit-Huguenin <petithug@acm.org> wrote:
>>> 
>>> On 8/9/20 12:23 PM, Joe Touch wrote:
>>>> 
>>>> 
>>>>> On Aug 9, 2020, at 10:54 AM, Nico Williams <nico@cryptonector.com> wrote:
>>>>> 
>>>>> Really, asserting that "master secret"
>>>>> is problematic is simply credibility-destroying.
>>>> 
>>>> Besides your concern, how does one secret actively control another?
>>> 
>>> You are insisting that the only possible meaning of "master" is to control some[one|thing] else.  According to New Oxford American Dictionary Third edition, that's true when used it as a noun, but not when used as an adjective or a verb.
>> It is not true for nouns either.
>> A master of science does not control science and a master of business administration doe not control business administration.
>> A school master (this is a British usage) is just a male teacher. He does not tend to control the school.
>> A chess master can beat me at chess, but he doesn’t control the game
>> And there are many more.