Re: IESG Statement On Oppressive or Exclusionary Language

tom petch <daedulus@btconnect.com> Tue, 28 July 2020 16:45 UTC

Return-Path: <daedulus@btconnect.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 A6E6A3A0E24; Tue, 28 Jul 2020 09:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 HILshffkvyis; Tue, 28 Jul 2020 09:45:16 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2121.outbound.protection.outlook.com [40.107.22.121]) (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 7980C3A0E89; Tue, 28 Jul 2020 09:45:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Q240UdW49T9SXh/Il6auR0TL12MqjP78kS73zVyaRYQoyCUagyhaKnBGV4LHyzzEmru4lhrZ9jbEz7OsyXVXzOPXSZK/ytpzRng0AwFbX5RxfNQSRo6ChL2YWm3ZgQkO/ubTNFF5k5S6o4P9F7F+98CmnTRV48CzxzodWZ38C9z3O6cWjjOXwfsFTV9mPNBNcdYzACHtCkdknZRWwDtXw92059Ay5rFxKovQkBiEcUkkPlw7hT/6sBZU54lXsGsmfsQWV8IxcPiK47KW782oydBMGdWs18EapJOEZq++6eANzhJ1ByuPvqH7xWVYhFZDn5NA7ZdzBCziwWNTtI8c3A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=T4Vfsze3VdqAYncJH3N0ZQtCOfL0HkA3PQzylYkAxI0=; b=XAi0QIvSbGSLDFrPtv+8J1CafL99bjp4NVgaMeonFAIF+bsbpT3wMN2SboK/gcxwTKsIaPZC9ez3IRLDQYj7MgaNGRmecLcuSClvVzzOwptENHhvd7EIsGk1bvjnEa7W2mbknOr5rbJOV6OGp9YWyGOS74Ae66OUlm2zWaSdmXQtC46tkf+cV1rBHEpk+7x7BDA6Xa6NQEKiTM4+TSBUULaSHnDvul6Hyhn8cnZI68VZfO2VPbESUkajnckKBmR8uiay7fL2ASCIV3/60plCIDw8ZEOrDrI7KI53EMUlYO19B/kNFj1DV/6g9PjJv8tA17H1IzhelgmMDzqrEhoM8w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=T4Vfsze3VdqAYncJH3N0ZQtCOfL0HkA3PQzylYkAxI0=; b=e+5K12feKv1HVEV5DT7kCiKPVntDR6xmwXZFgqaL3PYmiUujCWlytIlmuDPSqGQ6afGleYbP5EU29fM19B9BaeRhzmGI+iLCLA5hxWyWx5er5zzKjqdQ/oe4OlVTkQzbhYBY1JmYvmCoa7ycy4asKj+glB4n/uIZP+itOl4sc38=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR07MB5805.eurprd07.prod.outlook.com (2603:10a6:803:d7::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.9; Tue, 28 Jul 2020 16:45:07 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::bc6a:1add:e84e:f19b]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::bc6a:1add:e84e:f19b%9]) with mapi id 15.20.3239.015; Tue, 28 Jul 2020 16:45:07 +0000
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
To: Nico Williams <nico@cryptonector.com>, ietf@ietf.org
References: <159552214576.23902.6025318815034036362@ietfa.amsl.com> <20200728160033.GE3100@localhost>
Cc: IETF Announcement List <ietf-announce@ietf.org>
From: tom petch <daedulus@btconnect.com>
Message-ID: <5F20560F.4090701@btconnect.com>
Date: Tue, 28 Jul 2020 17:45:03 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <20200728160033.GE3100@localhost>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: LO2P265CA0001.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:62::13) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (81.131.229.35) by LO2P265CA0001.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:62::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3239.16 via Frontend Transport; Tue, 28 Jul 2020 16:45:07 +0000
X-Originating-IP: [81.131.229.35]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: d06f6c31-4702-44fd-f904-08d8331595f1
X-MS-TrafficTypeDiagnostic: VI1PR07MB5805:
X-Microsoft-Antispam-PRVS: <VI1PR07MB5805F9997494EB859B636575C6730@VI1PR07MB5805.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: MSepr7YdUz0/mg2OC7j6Al0TdFtcTqaQc9VoQHGfXpgnCHt11FBfdI6QHrhsKdAbzFFyJCsTuHzpQCqTdJNsMb4wukqur0wVVpkYf155JrQ3j4+Zi89cB393vi3WEMng2DZLpSG4fz0lHlRvAErTVqurdQwbM88RhcIpHVToUhc7DqGbpyocoTfDdaJnUpkd7usZ0h1+29xuIy7LeFDgsMxbhvpRokvzvqF8L9WhjTVLq1R2uOW6HEgpACM/i2Tp3x2Y2HNGjcE5UkHYw6/FnF7Y0hLzjJR7q5kkeahsTOiluYYKwbMEKQJkFeVgi4Ii7DIyocGz7iFpTTU7paI/vFtjP1cYrNzKaYiL8RhgUazvnntvVUIKoaLhVFqXoMvvRnHaG7rvcQGmRP7PLPekJg==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(39860400002)(346002)(396003)(136003)(366004)(376002)(6486002)(16576012)(86362001)(316002)(2616005)(36756003)(956004)(53546011)(33656002)(4326008)(6666004)(5660300002)(52116002)(83380400001)(66946007)(66556008)(66476007)(8936002)(87266011)(26005)(16526019)(966005)(8676002)(478600001)(186003)(2906002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: N67C3RgSYHVQLTdRQWy7xGtojv8niw8Vx+0RXF+WKHuZqZesXOWFu+2Scj9EMazjtnB7tVUqVNiZZnQqicMczrC1Yz9C4OjVgNKelFfxAcfcVN+UI6CdN7bhR79krNEJh7Cj1YZwGGr58yPBkEK5pxAtqnrIVeXoAq2Qfb1B02Vg1nqqEcJYtDvLxWp7vv7RNBpKBtXdDtx/SDMf1mrZpa6zWRnMWo7SeT570KWkb85LKXRPXXVcuvAC3bYXspmlp8xYDAypMpib/Z3b8HTjzDQQj9eJR7dF7GNIjBPT2QQ2zm2xuoFei7idzoMSfbrn32d0YiOqHp1M7b2ztaD5XbDrTDdXZgzpzoWAblX9qDhEIxBnhbmVT579yHTgQJHaGNlbl9dx6K87NMNmCVbp6oQHRzvrW9HQ364Y3c0HCtRfUR0pwtA/bQb+XDdhKmyeKZiDA03k19PWkjZWnZ0fNpkadNXp3BnGQk7wjeyqvORgOj3dIWztpr6NlKYtWFixTUUdtJbDh9xDQDC7I3Xvjd988gjiiiCL8Dk6m/4AejKH2l6JL9A8urcfoQx5q/JUoCctT+AC/VxBZYWR0hsq3/pg5g6tQQNGnAzLIs4j/uUBdxB7sQKrKvZxFPLePxFixo2eN1dGC4h2p6gjk48XvQ==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d06f6c31-4702-44fd-f904-08d8331595f1
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 28 Jul 2020 16:45:07.7411 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: WPnfi8Bfcptp8xUcTIGcf2G8g5EAKU5l7XM2UUQy6IfcfdpZfd2NbRlh0pLv6yp/JSsaNkc6Pavszt+rqL2x6A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5805
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T3NMrqMS29BD-Hl8q1InBjAA5Vo>
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: Tue, 28 Jul 2020 16:45:19 -0000

On 28/07/2020 17:00, Nico Williams wrote:
> On Thu, Jul 23, 2020 at 09:35:45AM -0700, The IESG wrote:
>> [1] https://datatracker.ietf.org/doc/draft-knodel-terminology/
>
> I'm surprised not to find there anything like a survey of RFCs, current
> I-Ds, and maybe even expired I-Ds, of problematic language.  Or any
> analysis of the prevalence of problematic language and trends in its
> use.  Did we use to have a problem that we now no longer have?  Do we
> still have a problem?  Is it getting better or worse?
>
> Can we ask the author, and/or maybe the RPC, to perform such a survey?
>
> (The RPC presumably would only survey RFCs, not I-Ds.)
>
> It would be quite useful to have such a survey.

Nico

Uplist you will find an e-mail from me about blacklist which showed that 
in my own local (statistically unsound) filestore of RFC and I-D the use 
has much declined compared to 10 years ago.  I think that that is one 
term that we have informally recognised as unsuitable and acted upon 
without any need for an IESG statement.  (I was responding erroneously 
to a post that was about black magic that I thought was about blacklist 
from Rich Salz).

At a tangent, I keep looking to see if my posts have got through the 
rules imposed by my ESP; if I ever refer to the LSR routing protocol 
that is not OSPF by its usual abbreviation, then my post is .. well, 
disappears without trace.  You can guess what word I was about to use:-)

Tom Petch



>
> Nico
>