Re: A contribution to ongoing terminology work

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 02 April 2021 22:35 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 BD3773A08A5 for <ietf@ietfa.amsl.com>; Fri, 2 Apr 2021 15:35: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 JS0cYf8loUEZ for <ietf@ietfa.amsl.com>; Fri, 2 Apr 2021 15:35:36 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (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 21CBF3A089A for <ietf@ietf.org>; Fri, 2 Apr 2021 15:35:35 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id ot17-20020a17090b3b51b0290109c9ac3c34so5154442pjb.4 for <ietf@ietf.org>; Fri, 02 Apr 2021 15:35:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=b1ubHKLH1WTAgXDFy5Zau7r+/P0wNGMGtIZT/8pXkwk=; b=gwafJDmLRg6pi05beljXNFWtU9y44lMvJdBVyjLPweoxZQZkW2b5xqGD3zR4zpbdK/ rjzKhEWpIOOxh8A7IEXlgye1gBoHPweMvN1yfHWmwOYpuZ3BeVXIxmoTYrBLsCN1zUTJ 7x9knYBI8DJEz6CQyE2oWgXr6h0jQ2AGbwv7UdcqLRm1GKplQqwtE4YyDrbVNwNqvUS7 sA9Xsp582cZMY443zRrVfdn8QcPyth5/FokaSikY2+ggPYxd8lyNgDUGnnjpUYfhVRqr o6k/rW1taFpsATgH1SzU87xT+e88P7ZuUsftSLhw0qVeH7AgcxdYnNL8C3LhgTGOGTrX m4pQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=b1ubHKLH1WTAgXDFy5Zau7r+/P0wNGMGtIZT/8pXkwk=; b=sPTaTDUpFKKo/fcXo6l5Ow0oDqz5KLbGTydWnX4QysRPIcR94G+fo3ap9gpXNWH+EC L5FZtBkKr8KdLXhzUdxr7Scj7Il/895/fjDSNQg4lHSf8l/a3JdSXlJYTiVl+Zazhzl9 3H8+rVD7VYhQCTcfnvl4ZcB5bUvpxiAzcv1moRTSFu38v8OyE67sAdHTKd125tUQIXvI OPpbORMPfv7E5rj1c4nbOT7ptaA4PSMVZ6k4p7I+XuFZC8pUd0KbXUnXYgjwvQp3l+aO 6xw6rSofpBRbFintK4npyxgi2Zvqj5yjF0ev+8hT4tEPNX/J7eAlSMCyGF74hyq00aqL 0P4w==
X-Gm-Message-State: AOAM533NRGOXxVOPjEURQqCM2xtt1ah9tfm6tbkB97Q69JmkcSoEyHsv M/aOytdzVb0EWkMEykBMonY10Echi0uRpA==
X-Google-Smtp-Source: ABdhPJx5OdQ9B9vVpV+dfaxZ9mDQ0Z3YQZ+dzCWH5PZURQ6AEgxgwSRZqlZVEK+duJOmyl45bYRNcw==
X-Received: by 2002:a17:902:e844:b029:e8:ca1e:4118 with SMTP id t4-20020a170902e844b02900e8ca1e4118mr2942660plg.63.1617402934515; Fri, 02 Apr 2021 15:35:34 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.131.14]) by smtp.gmail.com with ESMTPSA id l20sm9249816pfd.82.2021.04.02.15.35.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Apr 2021 15:35:33 -0700 (PDT)
Subject: Re: A contribution to ongoing terminology work
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
References: <859352252.4167919.1617264911078.ref@mail.yahoo.com> <859352252.4167919.1617264911078@mail.yahoo.com> <85575541-C896-4530-B028-C0DF9BA3EA8B@ietf.org> <411426886.24320.1617306016731@appsuite-gw2.open-xchange.com> <20210401195735.GA3828@localhost> <20210402032059.GD79563@kduck.mit.edu> <1e4feea2-2c81-b31a-04e3-d4c9a4adbaf7@lounge.org> <20210402163230.GH79563@kduck.mit.edu> <4c82de79-1e40-2eed-909b-8a288284393d@lounge.org> <439a33c9-5791-4c90-76a3-54aab828a37d@network-heretics.com> <5C955F3B-2EE7-43DD-85BA-DA1C1CF353F1@tzi.org> <7b3ba302-ec36-eb8d-7461-861a0b6651ac@network-heretics.com> <0dca7a0d-d51e-4c67-cc96-a44de0141480@gmail.com> <9c369a34-d47c-3af0-9793-8342f5f6ec63@network-heretics.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <c613095d-f0b4-8df7-e703-d1b3c52bffc5@gmail.com>
Date: Sat, 03 Apr 2021 11:35:29 +1300
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: <9c369a34-d47c-3af0-9793-8342f5f6ec63@network-heretics.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/jeaQnYKrP87cdsfyiDshO_fKE6s>
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, 02 Apr 2021 22:35:38 -0000

Keith,

On 03-Apr-21 11:02, Keith Moore wrote:
>> Indeed. Judging "intent" is very difficult except in the most egregious cases. It's much easier to judge offensiveness: if a reasonable number of people are offended, it's offensive, whatever the intent. 
> 
> I would not agree with that definition, or wouldn't find that concept of "offensiveness" useful in determining whether it's appropriate, because quite often I find that people have strong adverse reactions to things that need to be discussed, but they can't get past their reactions to see them.

Yes, and when that happens in a technical debate it is very damaging. I could give examples, but that would undoubtedly start a whole side debate about each example. The current context is not a technical debate, though. So I don't have a better definition than to say that something of a sociological nature that offends the majority of the audience is offensive.

>> FWIW, I found the "Les White" drafts pretty offensive, and unprofessional, even if I could discern a satirical aspect.
> 
> I wish we'd stop using the word "unprofessional" because it's such an ambiguous word.  

Yes, it isn't ideal for the reasons you give below. I don't have a better single word though. So: I found the "Les White" drafts seriously inconsistent with bullet 1 of section 2 of BCP54: "IETF participants extend respect and courtesy to their colleagues at all times."

Regards
    Brian

> I've heard people accused of being "unprofessional" because they wore a hairstyle that made sense for the kind of hair their bodies grow; I've heard people called "unprofessional" because they dressed in clothes from their own cultures (even though there was no prescribed dress code).   I've heard people accused of being "unprofessional" because they respectfully expressed technical disagreements with their bosses.  I've heard people described as unprofessional because they weren't herd creatures - they had different ideas than those of their colleagues.   So I've come to think of "professional" as just another kind of arbitrary prejudice that we'd be better without, an excuse to harass people who think differently.  
> 
> So I wish we'd stop trying to make IETF "professional" (at least in those senses) - I think it impairs our ability to understand this hugely complex system that we've created, impairs our ability to function as responsible engineers. 
> 
> But if we're going to use the word, we need to define what it means for IETF.   For IETF, professional should mean things like treating our fellow participants with respect, but NOT expecting people to accept ideas and proposals without question.   Professional for IETF should mean making a genuine effort to contribute to consensus if at all possible, but without expecting people to buy into whatever proposal the "right" people are supporting.   It should mean letting leaders do their jobs in managing process, but also being able to question their actions, and treating them like peers in technical discussions.   Professionalism in IETF absolutely SHOULD NOT mean acting like people are expected to act in corporate environments.  
> 
> Professionalism in IETF absolutely SHOULD NOT mean never making people uncomfortable.  Willingness to be uncomfortable is a necessary condition to do this work.   This is not because people should try to make others uncomfortable for no good reason, but because/trying to wrap your head around someone else's mindset to see why you might disagree and how perhaps to craft a compromise is inherently uncomfortable./ 
> 
> I remember the first IETF meeting I attended, in St. Louis circa 1990.   I was a starving graduate student who showed up because friends encouraged me to go and paid for my expenses.   I got to the hotel where the conference was being held and realized that I hadn't even thought about what to wear - I was wearing the t-shirt and shorts that I normally wore around campus.   I wandered through the hotel looking  for where the conference might be and discovered a large group mostly wearing t-shirts and shorts, and realized I was in the right place (in more ways than one).
> 
> IETF has always shunned the trappings of professionalism, much to its benefit.   It's survival as an effective organization depends on this.
> 
> Keith
> 
>