Re: IESG Statement On Oppressive or Exclusionary Language

Joe Touch <touch@strayalpha.com> Sun, 09 August 2020 19:58 UTC

Return-Path: <touch@strayalpha.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 27FA53A0D3B for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 12:58:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 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, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 16rCNhhj4D7m for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 12:58:51 -0700 (PDT)
Received: from server217-4.web-hosting.com (server217-4.web-hosting.com [198.54.116.98]) (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 C8AB33A0D3C for <ietf@ietf.org>; Sun, 9 Aug 2020 12:58:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Transfer-Encoding:Content-Type:Sender: Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender :Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=o3xYgAZGFt9pH7TDN96namPi22jMBhzODS3wHPCjmto=; b=wRELPUp4GECxkNUShU37Y0aVKm VcVyCoU2qKHt5mwJVysV41VXkINkUeYsAkj0H8HwJoH2g/UoIWsz8exBjAXrUCQ7gXuFJvKq457TQ WqNBeDoR5pN7mqGPqZtrRLcjbk6v6191w6nXN8E7+6CrWXtyEMxI2O+qp9Tl3PcEZ8psX0bkPYMaK Pub6iFi5pqs96Av5DozPkQgX7JTsyI1rkn/y7Xa0nt7C+l/FC7TTpxibXoIDoUzC7utPkMLoCWLdM K5fOe73nZn3WBmqqYcdwka9nAK7jleA9zD9xXg/W8R7fmjfSS91YKKqejXYaTHqfyNAPAoQd/61LR RyUZ4eAw==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:55103 helo=[192.168.1.5]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <touch@strayalpha.com>) id 1k4rSx-000SUx-IK; Sun, 09 Aug 2020 15:58:51 -0400
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <45d477cb-7cca-55c7-c4f1-d12cab784997@lounge.org>
Date: Sun, 09 Aug 2020 12:58:47 -0700
Cc: ietf@ietf.org
Message-Id: <1C71E46D-E3D8-441D-8131-83128FDEDD94@strayalpha.com>
References: <45d477cb-7cca-55c7-c4f1-d12cab784997@lounge.org>
To: Dan Harkins <dharkins@lounge.org>
X-Mailer: iPhone Mail (17G68)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BTyjWHSdT020L3K_T8JZOxO1RRw>
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 19:58:53 -0000

In physical locks, the master is the common key. It doesn’t control the other keys. 

In crypto, the master is the root or primary; others are child or derivatives. It doesn’t ‘control’ them either. 

Most crypto texts and docs need to explain that because it’s not understood from the terms alone. 

Joe 

> On Aug 9, 2020, at 12:50 PM, Dan Harkins <dharkins@lounge.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?
>> 
>> Or is it just that there is one root key from which others are derived?
>> 
>> Ie why even bother defending a term that’s inaccurate to start?
> 
>   It's not inaccurate.
> 
>   In locksmithing a "master key" is one that opens all the doors while a
> non-master key (which is not called a "slave key" by the way) only opens
> the door it is milled for.
> 
>   Analogously, in cryptology a key can be a "master key" if possession of
> it can be used to decrypt all the different traffic flows and a non-master
> key (which is also not called a "slave key") only decrypts the flow it
> was generated for. It's a great term.
> 
>   You can even get key hierarchies and the analogy holds. There could be
> one key for all doors in the building and separate keys for all doors on
> particular floors and then keys that are specific for particular doors.
> Similarly you could have a key that could be used to decrypt all flows on
> all cluster members, a separate key that could be used to decrypt all
> flows on one cluster, and flow-specific keys that just decrypt one
> individual flow on one cluster. It's a great term.
> 
>   Asserting that use of "master key" or "master secret" is a problem or
> that it somehow "discourages participation in the IETF" (which is what has
> been asserted for this new category of Problematic Words) is absurd!
> 
>   Dan.
> 
>