IETF Logo Mail Archive

Re: IESG Statement On Oppressive or Exclusionary Language

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 24 July 2020 04:13 UTC

Return-Path: <brian.e.carpenter@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 081003A0AD3 for <ietf@ietfa.amsl.com>; Thu, 23 Jul 2020 21:13:37 -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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 KvLw6_A9c8Bp for <ietf@ietfa.amsl.com>; Thu, 23 Jul 2020 21:13:35 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (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 60C3B3A0ACE for <ietf@ietf.org>; Thu, 23 Jul 2020 21:13:35 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id gc15so5269420pjb.0 for <ietf@ietf.org>; Thu, 23 Jul 2020 21:13:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=dSEKBHhDHsBKK8flwxnuzqu3H8eCRMdYh/zLznXpdIo=; b=ohvvLTt+C/zY8aGtuHy3FjGh+QhCXO++PHrAj+juq8JMMbl7wRhyin8XwpdoJKhVTn zau2TBRPmhj6dNSYAwqrzRChd7Vb1piigiUgEpmI7hkQ9Kyuw82m6W6klIBNfyvKzkPx QTdE18fYWWagtEBH7cDIrDuAfffgO7dRjBqjKRgQrXymWoTFVbo/NrxKHcgTuaYKskZo cwMcod28vaALFjEMo+9s4RtTXmPdOlexzhDDioMaTuojYW1nEK0yqK3XLg4Pbyep9E1o EppQfzX5K/r3QBgBqw9F+eRyiFRqrGpJoG5PBQakJxuAJPSzoLYcD4Vml5GfT+p/SUvN SJAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=dSEKBHhDHsBKK8flwxnuzqu3H8eCRMdYh/zLznXpdIo=; b=JfvhVokpH/mT5sYXSXWQ8STjasVqn8AnNVIBBbKgjMFYtUh4yZ0FQtADeC72Re7iil eGfBz5yazQ1x1C/7YUuZQYplynWIYe/5Ter2kqW1c8Rk1ru2ST+vM0g9NSyp6SBrmRph gxCTg/eacweyG+t2qvh6Orbeg3xg3VuREQOE0INEi1GcSn27c/DWDVYhpPMcNFH9AZKK UKdMMjqJiBLfCWhfdfkTtfGak655YG1VSHdk78Oh9e+ZXAHqb0P3okjdnvzaWbxGr61B II7DNsF1ALGImTV2aF52BGpdDr2zGEjmxFZ6jpVxA+7qonl8tWQFSUUS8Su9Y1abKD+J 6oVg==
X-Gm-Message-State: AOAM530MgWKHhd6puHni7Ho/b4jbs1sM2YNSZdryYdcwvVGEZ1/v9n+Q e8BhYTYPieLTvs9vD0S5Ktvpojq0
X-Google-Smtp-Source: ABdhPJyneOwNZaF25kbJc62NI6n2WLDMAiZ62d1JB+oAESmkjfZqPmCSqlJXIOvZsTHugkeZYo4jkQ==
X-Received: by 2002:a17:90a:1a83:: with SMTP id p3mr3266360pjp.113.1595564014520; Thu, 23 Jul 2020 21:13:34 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id a68sm4365210pje.35.2020.07.23.21.13.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Jul 2020 21:13:33 -0700 (PDT)
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
To: Joe Touch <touch@strayalpha.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, ietf@ietf.org
References: <2c018854-bfc1-e014-6e5d-2ed799a6a602@gmail.com> <A73CC96D-7819-4CE6-A061-46003D45391A@strayalpha.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <16bcab50-0b00-97dc-8b51-7b444ea45cea@gmail.com>
Date: Fri, 24 Jul 2020 16:13:29 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <A73CC96D-7819-4CE6-A061-46003D45391A@strayalpha.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NRICwG3yerh9vjSZRZzFBn1C_Vs>
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: Fri, 24 Jul 2020 04:13:37 -0000

On 24-Jul-20 15:45, Joe Touch wrote:
> 
> 
>> On Jul 23, 2020, at 7:34 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> "Master" on its own is here to stay, anyway; in some contexts the proposed alternatives (like "main") simply don't work.
> 
> I have no idea why you could claim one works and the other does not.  
> 
> Master of what?
> 
> There may be better alternatives, such as canonical. 

"Canonical" applies in some circumstances but not always. You can sometimes use a
complicated formulation like "Authoritative server". But if you need to convey that
the entity in question gives instructions to other entities, any word you choose
will be synonymous with "master".

> But “master” isn’t a unicorn word. 

It's very common word with multiple meanings and applications.

    Brian

v2.23.0 | Report a Bug | By Email