Re: IESG Statement On Oppressive or Exclusionary Language

Bob Hinden <bob.hinden@gmail.com> Wed, 29 July 2020 17:44 UTC

Return-Path: <bob.hinden@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 5BB043A0DFF for <ietf@ietfa.amsl.com>; Wed, 29 Jul 2020 10:44:34 -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 48RCK9hnOYuQ for <ietf@ietfa.amsl.com>; Wed, 29 Jul 2020 10:44:31 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 F26693A0C2A for <ietf@ietf.org>; Wed, 29 Jul 2020 10:44:30 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id z18so18888024wrm.12 for <ietf@ietf.org>; Wed, 29 Jul 2020 10:44:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=lm4CXNSdvwEgJffihvkDewjDqUoI3sA33WdB7TRMUEI=; b=E/HMH5ugVw9PzPnsAn5RuGW+Xi97PvIzdz8p7TMBQMV8AxNwtS86Ry5hgGbnIfnTES JJxFUrwFcMDTPsAMW1Lme155YZ/BSnK4m3HJeekMOhQ5QfE0iqhe60eAT2FuF19WvTSR ZZ3JUtvXYAn9VNqQloPovGlLGslTAF6c+vhzzEylBkBXvspB2nnULOK8fCBO/9cNYH/v 5b7VgMxek16nj9CUeNh++BTFH2ZZcEivBuBmUoies8BqGnvFKkpilWJRfC6Nse/7cCWh C3ZYGwRymSUU0lEQMBMD33JeNJWDoTaPQ+0Y31DR2/faS0OnaHeBXTVKslNqz/dd+WKj eNbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=lm4CXNSdvwEgJffihvkDewjDqUoI3sA33WdB7TRMUEI=; b=FTkVvrgMgFYOnZBbLzA677bQ3BDnx9nLECl5Ig99+f9KovSmpYJ92BmECzMw8mb19p 893mxrNMxcrpcZdKKPCe1bXwFTu/QtnxTsBIyDnlHdrqNtiVdP05TEwCrMIl6mVf7CCK TNgXwyqXtaTQDWXAdUYD1PsKY/P3Q/06YaUZDiRnDn6mixuXwgmItgwDi6zUCyaFmIfL Tew8jWc7S363NV8Qfsl50x8ADx04S9ZGqN7juPBZKRmr3GZ9FuXaElUyoRAZM4fzZO4x CF1VTg4rwREKa+bxVG+T6XwvmXpLHR9P8dkQFKA+IdCMRHlzSyGkukr07aIJ+GT5wD3U 0abQ==
X-Gm-Message-State: AOAM531wfO2ppX/78roCgm0iaIAKFYIOHGj3Mulk24hthi0cHZhlkZrU YNvrWZwDhzw2Azb9GgttF/A=
X-Google-Smtp-Source: ABdhPJwDd/k8lG6RLPwWfYEGyrsxTgmOP7c6RWPwz8gdSGQyPBdZ9ur+/Pe1CX3lzgmX33MTE/rytg==
X-Received: by 2002:adf:bb14:: with SMTP id r20mr30598008wrg.366.1596044669439; Wed, 29 Jul 2020 10:44:29 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:a1bb:b4b9:7e6:ac64? ([2601:647:5a00:ef0b:a1bb:b4b9:7e6:ac64]) by smtp.gmail.com with ESMTPSA id z6sm6753707wml.41.2020.07.29.10.44.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Jul 2020 10:44:28 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <150D4C9E-CE53-4A12-A90C-97F1C20B1AF1@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B1B2AFB8-1D3F-4625-9E42-8318ED673DA3"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
Date: Wed, 29 Jul 2020 10:44:15 -0700
In-Reply-To: <eb0feb43f71d4a8b8f9f1e7eec264b17@att.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: "STARK, BARBARA H" <bs7652@att.com>
References: <933ce8b4-78a5-76bf-55c3-7c5694faffbb@necom830.hpcl.titech.ac.jp> <267BCA35-3A3F-440B-9F5F-2C818D5AE71A@icloud.com> <e7956fd8-2639-3df6-9539-0dd483cafa25@necom830.hpcl.titech.ac.jp> <34CF64D6-10F3-4F45-B592-FA14C911DB0B@chopps.org> <c18fc227-7da0-1487-a2ae-74de1ac73759@necom830.hpcl.titech.ac.jp> <CALaySJ+UbSP5nJungBae053q7W_VQ-8yx2pr+KP6S+G81_1_VA@mail.gmail.com> <29896C76-F631-4E5A-9F42-CB9CEA08ABF8@gmail.com> <0A4009EF-5FF7-4BDD-9D45-33DEBC140CFD@akamai.com> <f60386ad-2dbe-4364-aa14-c8b8ceac46b3@www.fastmail.com> <d6ded405-d91a-5235-3f8d-5afacb490a11@mnt.se> <eb0feb43f71d4a8b8f9f1e7eec264b17@att.com>
X-Mailer: Apple Mail (2.3445.104.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bBpGYdEEjcGgkNv3gdZkPS_V0Rw>
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: Wed, 29 Jul 2020 17:44:39 -0000

Barbara,

> On Jul 29, 2020, at 8:33 AM, STARK, BARBARA H <bs7652@att.com> wrote:
> 
> Not replying to any particular email, but to the general discussion...
> 
> It seems to me that IETF isn't in a good position to natively determine what words are "problematic". So what I think would be good would be to have a list of words and phrases that external communities (e.g., governments, universities, corporations) are either forbidding or recommending against. Include a reference to the external community's web page where they discuss this. RECOMMEND not using words in this list. Allow anyone to suggest having something added to the list; suggestion must include the reference. Have a small team that vets the request (makes sure the reference works and judges whether the referenced community reflects a community that IETF should consider reflecting -- which is still a judgment call, but I think identifying whether a community is (or should be) important to IETF members is easier than judging whether someone who doesn't share your experiences might be offended by a word or phrase) and decides whether or not to add it to the list. An existing team, like the Ombudsteam, might be tasked with this.
> 
> The RFC Editor doesn't need to police the use of these words. Allow for IETF community self-policing to decide whether a WG or independent stream author really want to use a word or phrase, given its presence on this list.
> 
> For example, consider Apple as a reasonable reference.
> https://developer.apple.com/news/?id=1o9zxsxl
> 
> Specifically, for "master/slave" or "blacklist/whitelist", look at
> https://help.apple.com/applestyleguide/#/apsg72b28652 and go to master/slave or blacklist/whitelist in the alphabetical list

Thanks for the pointers, these are quite good in my view.

Bob