IETF Logo Mail Archive

Re: IESG Statement On Oppressive or Exclusionary Language

John Levine <johnl@taugh.com> Mon, 27 July 2020 20:28 UTC

Return-Path: <johnl@iecc.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 39C5A3A0BAC for <ietf@ietfa.amsl.com>; Mon, 27 Jul 2020 13:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=uPmEWjT9; dkim=pass (1536-bit key) header.d=taugh.com header.b=WKBihIU5
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 D4d0ny6RicsK for <ietf@ietfa.amsl.com>; Mon, 27 Jul 2020 13:28:52 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 39AEF3A0992 for <ietf@ietf.org>; Mon, 27 Jul 2020 13:28:51 -0700 (PDT)
Received: (qmail 47048 invoked from network); 27 Jul 2020 20:28:49 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=b7c6.5f1f3901.k2007; bh=pd1bAOr7l7TmtvWZ9b1mCkxltpLV7xuoGvFoFsHj1kI=; b=uPmEWjT9mWs8GUHZtxquqf/Q/zEEFTVBZRBgRdcoh3xsol/NtqHIvE42wA6UGvQ675s8koZpW++ce8MUDAzgNHe/YLNifpbN5Xt8WX2S9iVP5xDByhwfDOlOUzlTO3n47NsmjPoV+qD6PoGYdUT6YyPf1u9mByiWeUwdWOu7RMZWpa5Fks1kKtCr13OggXpVYeu8+bjRuDAX2Eti/xdAoN/Enj0IbndTDt+bYW30WAYNmuKNPIhu3yCpxy2VE32Y
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=b7c6.5f1f3901.k2007; bh=pd1bAOr7l7TmtvWZ9b1mCkxltpLV7xuoGvFoFsHj1kI=; b=WKBihIU5NUaVDKgBfw4sD4n/dC+jarlqTeGhqsS2IrgmfKWoArXXAO0wKuLSWSGRzXRLnckjIlwZNB/JEhLb79Z9SNh/CnbWk+vYoUGvHnjjQbhoEd79Z94P2f0xvTUo2wC4rMP7lqxfPe7ZKXJNy2vsWJgJEsfbIPNO1hi+ohYuUEqTBusq7fdBGEbeDisB2ezMAvjBMZMnYl3kqRvybFLUhudq/qMG8fppgn317hbn0bRL9rJMN8NjJVS4eId8
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 27 Jul 2020 20:28:49 -0000
Received: by ary.qy (Postfix, from userid 501) id CA8471D8F8F2; Mon, 27 Jul 2020 16:28:48 -0400 (EDT)
Date: Mon, 27 Jul 2020 16:28:48 -0400
Message-Id: <20200727202848.CA8471D8F8F2@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
In-Reply-To: <593D45F0-7452-4CAF-8478-95169205AFCB@gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OnPw1YUPpQEsJQ7if7EomJMyxBs>
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: Mon, 27 Jul 2020 20:28:54 -0000

In article <593D45F0-7452-4CAF-8478-95169205AFCB@gmail.com>,
Stewart Bryant  <stewart.bryant@gmail.com> wrote:
>No, I am describing the behaviour of one of the most fundamental hardware components in a computer.
>
>3.3.2 Master–slave edge-triggered D flip-flop
><https://en.wikipedia.org/wiki/Flip-flop_(electronics)#Master%E2%80%93slave_edge-triggered_D_flip-flop>
>
>It is the primary technique for crossing synchronisation boundaries.

>The historic term is master-slave, and whilst I condemn this behaviour in humans, it is an accurate metaphor for
>this electronic construct and the electronics is not offended by this required behaviour.

The master stage can sell the slave stage?  Still seems like a poor metaphor to me.

I suggest we call the two stages Eccles and Jordan.

Historically,
John

v2.23.0 | Report a Bug | By Email