Re: [Gendispatch] draft-knodel-terminology-02

"Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net> Thu, 23 July 2020 17:40 UTC

Return-Path: <ietf@gndrsh.dnsmgr.net>
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 B4B3C3A0C06 for <gendispatch@ietfa.amsl.com>; Thu, 23 Jul 2020 10:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.631
X-Spam-Level:
X-Spam-Status: No, score=-1.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.267, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 0hA0i4czPF1Q for <gendispatch@ietfa.amsl.com>; Thu, 23 Jul 2020 10:40:04 -0700 (PDT)
Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A192A3A0C02 for <gendispatch@ietf.org>; Thu, 23 Jul 2020 10:40:04 -0700 (PDT)
Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 06NHe3gY052972; Thu, 23 Jul 2020 10:40:03 -0700 (PDT) (envelope-from ietf@gndrsh.dnsmgr.net)
Received: (from ietf@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 06NHe37N052971; Thu, 23 Jul 2020 10:40:03 -0700 (PDT) (envelope-from ietf)
From: "Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>
Message-Id: <202007231740.06NHe37N052971@gndrsh.dnsmgr.net>
In-Reply-To: <6ce5efeb-c1d7-3c2e-17c7-432c3a5f66f8@lounge.org>
To: Dan Harkins <dharkins@lounge.org>
Date: Thu, 23 Jul 2020 10:40:03 -0700
CC: gendispatch@ietf.org
X-Mailer: ELM [version 2.4ME+ PL121h (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/iVHeKDNlbo0WkUo7KQLEuXIbr9A>
Subject: Re: [Gendispatch] draft-knodel-terminology-02
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: Thu, 23 Jul 2020 17:40:06 -0000

Hello Dan,
	Since you have brought up what I consider an excellent
path forward twice now, I want to chime in with a voice of support
for your tactic on what might be the best path forward for this
type of work.

	Though I must state the draft is better than most
things I have read on this subject, it still fells a bit
wrong from my perspective as well.  You summarize this fairly
well in your feedback.

	I do like the idea of addressing the poor quality
metaphore problem is a sound path that would benifit the
quality of the RFC documents.

Regards,
Rod Grimes

>  ? Hi Pete,
> 
> On 7/22/20 7:19 PM, Pete Resnick wrote:
> > On 22 Jul 2020, at 16:31, Bob Hinden wrote:
> >
> >> To Pete?s email, where should this work take place?
> >
> > See my other response, but this is part of the question the WG is 
> > meant to answer. Do we think we need a WG or BOF to work on this? Then 
> > we're probably going to suggest discussing on a new mailing list. If 
> > we think this belongs somewhere else, e.g., I could imagine that we 
> > decide that it should be part of the RFC Editor's responsibility, then 
> > we could ask the IETF Chair or LLC to take up the work. But we've got 
> > a whole menu of options. I'm happy to start talking about that now in 
> > addition to at our meeting next week.
> 
>  ? Well I hope one of the choices on the menu is rejection of the new 
> work. That
> was mentioned as a possibility laid out by the charter in your previous 
> email.
> And I hope I'm not out-of-line assuming that your offer of beginning 
> talking about
> the menu of options for the terminology draft includes rejection. So 
> assuming....
> 
>  ? In its current form I think the draft should be rejected. The racial 
> references
> are unfounded and gratuitous. Their presence in the draft is divisive. 
> The attack
> on some random person, by name!, for a comment on a blog in 2008 is 
> extremely
> unprofessional (12 years is a long time, Barack Obama was saying that 
> "marriage
> is between a man and a woman" back in 2008, the kind of thing that would 
> get you
> drummed out of polite society in 2020). We don't need to bring cancel 
> culture
> into the IETF.

Agreed, if it was up for WG adoption it should be rejected in its
present form based on your assertions.

> 
>  ? I did recommend some changes to the draft that I think would make it less
> objectionable-- remove all the accusations of racism and the discussion 
> of race
> and language, rewrite the draft to be more about getting rid of bad 
> metaphors
> which may not have universal understanding-- but that would also remove the
> potential for virtue signaling and remove the need for having purges of 
> bad words
> that represent bad think.

+1 again, the key being "getting rid of bad metaphors."

> 
>  ? So I guess from my perspective it depends on what the authors want. 
> Do they want
> to establish the word police to hunt out bad think (and bad thinkers!) 
> or do they
> just want clearer and more descriptive metaphors used in RFCs?
> 
>  ? regards,
> 
>  ? Dan.

Regards,
-- 
Rod Grimes                                                 rgrimes@freebsd.org