Re: IESG Statement On Oppressive or Exclusionary Language

Victor Kuarsingh <victor@jvknet.com> Sun, 26 July 2020 22:26 UTC

Return-Path: <victor@jvknet.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 744803A0B52 for <ietf@ietfa.amsl.com>; Sun, 26 Jul 2020 15:26:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=jvknet-com.20150623.gappssmtp.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 oe2XZBeHSZ1j for <ietf@ietfa.amsl.com>; Sun, 26 Jul 2020 15:26:39 -0700 (PDT)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 1161F3A153A for <ietf@ietf.org>; Sun, 26 Jul 2020 15:26:37 -0700 (PDT)
Received: by mail-wm1-x336.google.com with SMTP id f18so3541156wmc.0 for <ietf@ietf.org>; Sun, 26 Jul 2020 15:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jvknet-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7bQB04hrd2wm9o6t8juvKfN6ND7YnEN7XHeJaEV9HTc=; b=U+d1UbIR068KlREHoXkItUSF7AuG3UASO5mWFfwU8T9IEr0q2e5YgCDVGohKnVxptb ZaH13TSRY53V+/bVdWGh9+9aDiej4rifFMCUCn9Nh5F6c68RzWRdaYVSKemVwtVJRxva /PlLszgSEJIPn6rcFR2MjS4YBQsNoIuLAuDiAUrqewma38z+H3rfW0UMM2DvOlFqY+qR 6wu3SJZ0pjsougc0kqMbaaw/m7m2VxDPGL1kTJ4oakF2oVyQYJNYSP4zBanCDB1Cd4x7 JHwpKVtE17466PutR0jlO9QyzvUPWBRXfdFn5+jf/vk/E7KkAVs1SGZsscfkvoGi5r9B gBCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7bQB04hrd2wm9o6t8juvKfN6ND7YnEN7XHeJaEV9HTc=; b=YxIWXydVknZ4MfHWokZnyTIsO2G/0JdDNPRlNJTOqmIN+kxWqC4OwHAPotiNCIzs5Z WKpbWpBKIoV50LB/Kv5Lyy3vcvJUJqsQGKnZ5L0VpRex2I4/28SwB2rpMGBd9Il7xL9K KZBta6Rik3UZ+7slPouw2ZKhpeZqiXhpxO0deKYCmtVKrSaZ/RC2cW8ZYhvQGAdN3D6l EyxF4CRmh3PWXtDOUqVoDh43sjEHeKrlspOxC/PD3nmV+IlKVKcorsdSKSdpw7cT14T3 YQMpCQpk2DSgbIgYdwIfs+Vu51rqJuhVZ8Vlc0CS51fXphrHq6k7jg84xSaRV5Fslod0 rVvg==
X-Gm-Message-State: AOAM531POG3Y7bYLlx0NMmmF4Vktd9Tn1yt81XKJUXVwCwSbQjTSTNQ8 W8LZ5wT3MNieaGOMvxsrbgsvdYAvnooXx1gO2oTzPg==
X-Google-Smtp-Source: ABdhPJyXpTxv7gOC/XbnqpC3YoGf1wsiUNfDHbkTK25bChLebiRHKtvP6jfFspRWQsbKPWfr42dMrCO3c07AU05LCbk=
X-Received: by 2002:a1c:7d95:: with SMTP id y143mr15362096wmc.45.1595802395319; Sun, 26 Jul 2020 15:26:35 -0700 (PDT)
MIME-Version: 1.0
References: <159552214576.23902.6025318815034036362@ietfa.amsl.com> <dc32abdd-d361-a81b-a61d-4f4f69443e22@si6networks.com> <6E23B161-6CA0-40D1-A37A-6F0F79A90EB2@strayalpha.com> <cc5ee354-8307-a8ab-bfe0-522dc593d43d@acm.org> <EBDE082B-5663-47A1-820E-EBAEC75A36DC@tzi.org> <30F40837-55D3-4504-8310-AD387B156408@ietf.org> <B3D005AE195B6A0A766222B2@PSB>
In-Reply-To: <B3D005AE195B6A0A766222B2@PSB>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Sun, 26 Jul 2020 18:26:24 -0400
Message-ID: <CAJc3aaPSn89-MwZt9_A5eOi98LHokkvAZtUxeW0zyFJ4B1tTaw@mail.gmail.com>
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
To: John C Klensin <john-ietf@jck.com>
Cc: IETF list <ietf@ietf.org>, Jay Daley <jay@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e7b27805ab5fb27b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/te7EIU1JPpmLPYan0YX9TZUovSY>
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, 26 Jul 2020 22:26:43 -0000

John,

I am wondering if master/copy would be appropriate since that is what do we
in a number of cases.

As with things like recordings (e..g music, video, etc) , we have a master
of information and copies which operate quite independently.  This use of
the term - “master” -  is not connected with the historical issues with the
previous terms.

Not specifically advocating for this per se.

Regards,

Victor K

On Sun, Jul 26, 2020 at 18:12 John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Monday, July 27, 2020 09:32 +1200 Jay Daley <jay@ietf.org>
> wrote:
>
> > A question I can't resolve by Googling - has anyone
> > attempted to create entirely new words to represent the
> > concepts that master or slave have been used to represent?
> > e.g. a word that means "authoritative source of data that has
> > no dependency on another source" and has no other meaning?
>
> Jay,
>
> At least in the DNS sense, some of us (despite being old white
> guys with white beards) have objected to "master/slave" for
> years, not just because the usage may be offensive but because
> it is wrong technically.   In that context, the so-called slave
> is actually fairly independent.  It (or its operators) decide
> when check for and fetch relevant values (whether based on
> timeouts or on server request) and can reject and not install
> such updates.
>
> Unfortunately, in the DNS context, "authoritative" means someone
> else, but "primary" and "secondary" have been used for years.
> Of course, someone could probably find those offensive too, but
> then we get into problems with, e.g., "Director" ("Executive" or
> otherwise).
>
>     john
>
>