Re: [Gendispatch] Meetings summary

Dan Harkins <dharkins@lounge.org> Fri, 16 October 2020 21:05 UTC

Return-Path: <dharkins@lounge.org>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80FDA3A0B02 for <gendispatch@ietfa.amsl.com>; Fri, 16 Oct 2020 14:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level:
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.213, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 bU2K8GQIhVSy for <gendispatch@ietfa.amsl.com>; Fri, 16 Oct 2020 14:05:29 -0700 (PDT)
Received: from www.goatley.com (www.goatley.com [198.137.202.94]) (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 961573A0B08 for <gendispatch@ietf.org>; Fri, 16 Oct 2020 14:05:29 -0700 (PDT)
Received: from trixy.bergandi.net (cpe-76-176-14-122.san.res.rr.com [76.176.14.122]) by wwwlocal.goatley.com (PMDF V6.8 #2433) with ESMTP id <0QIB04R1LBX5M7@wwwlocal.goatley.com> for gendispatch@ietf.org; Fri, 16 Oct 2020 16:05:29 -0500 (CDT)
Received: from blockhead.local ([69.12.173.8]) by trixy.bergandi.net (PMDF V6.7-x01 #2433) with ESMTPSA id <0QIB00ACRBRAKU@trixy.bergandi.net> for gendispatch@ietf.org; Fri, 16 Oct 2020 14:01:59 -0700 (PDT)
Received: from 69-12-173-8.static.dsltransport.net ([69.12.173.8] EXTERNAL) (EHLO blockhead.local) with TLS/SSL by trixy.bergandi.net ([10.0.42.18]) (PreciseMail V3.3); Fri, 16 Oct 2020 14:01:59 -0700
Date: Fri, 16 Oct 2020 14:05:27 -0700
From: Dan Harkins <dharkins@lounge.org>
In-reply-to: <37C4EBD5-F9FC-4814-98F5-6926E2D4A66A@cisco.com>
To: gendispatch@ietf.org
Message-id: <a92579d4-acde-4515-3e1a-b396c82f0c7a@lounge.org>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_qP2QtNALTcom8d2vylHcuQ)"
Content-language: en-US
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
X-PMAS-SPF: SPF check skipped for authenticated session (recv=trixy.bergandi.net, send-ip=69.12.173.8)
X-PMAS-External-Auth: 69-12-173-8.static.dsltransport.net [69.12.173.8] (EHLO blockhead.local)
References: <B1075198-D4F5-498B-B16B-3081A9B07DDD@episteme.net> <76d19c8b-68d3-465f-b869-c18a9db7504f@dogfood.fastmail.com> <37C4EBD5-F9FC-4814-98F5-6926E2D4A66A@cisco.com>
X-PMAS-Software: PreciseMail V3.3 [201016] (trixy.bergandi.net)
X-PMAS-Allowed: system rule (rule allow header:X-PMAS-External noexists)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/MPH7H6NFgLIcdRG-0tq45Tgo_wA>
Subject: Re: [Gendispatch] Meetings summary
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2020 21:05:31 -0000

   Hello,

On 10/16/20 6:38 AM, Eliot Lear wrote:
> Bron,
>
>> On 16 Oct 2020, at 15:02, Bron Gondwana <brong@fastmailteam.com 
>> <mailto:brong@fastmailteam.com>> wrote:
>>
>> Oh I'm glad I missed this the other day in my "jetlag" induced stupor 
>> (I've been attending CalConnect virtual conference from 2-6am 
>> Melbourne time this week), so I didn't get dragged in at the time.
>>
>> I was very disappointed that the key question that I think needs to 
>> be answered by the community, and particular by those who favour 
>> draft-knodel, didn't have time for proper discussion at the last 
>> gendispatch meeting.
>>
>> *Does the IETF have confess to some "sins"?*
>
> With regard to language, it seems good to recognize that there are 
> phrases that we should avoid.  But I don’t know if that is the same as 
> a confession, or that we have to beat our backs on one to address 
> language.
>
>>
>> I believe this is the core issue underlying much of the 
>> disagreement.  I feel that there's not consensus on whether we have 
>> something to apologise for.

   I agree with that. Individually many of us may have things to 
apologize for but
organizationally, no, I don't think so.

>> There's also a sub issue hidden under that, which is this question:
>>
>> *Is the IETF systemically racist?*
>
>
> Is that the effort or is the effort to correct language?  The above 
> question seems to me a great opportunity to rathole forever.

   "correct language" for what reason and to what end? Addressing the
short-comings of  the English language are not in the IETF's bailiwick. We
should strive to use clear metaphors that can be understood by people
from different cultures and who do not have English as a first language.
I think there is consensus on that. "Correcting" language in order to
address a demographic issue that some people have raised is another
matter though.

   It's not clear that our use of language is the cause of any demographic
issue we may have and it's not clear that "correcting" our language would
have any impact whatsoever on the demographic issue.

   For instance, replacing a commonly accepted cryptographic term of art
like "master key" with something like "main key" will, IMHO, have
absolutely no effect on systemic racism or any demographic imbalance
in the IETF. Why do it then? Why are we having this exercise?

   regards,

   Dan.

-- 
"The object of life is not to be on the side of the majority, but to
escape finding oneself in the ranks of the insane." -- Marcus Aurelius