Re: [Gendispatch] WG Review: Effective Terminology in IETF Documents (term)

Pete Resnick <resnick@episteme.net> Tue, 13 April 2021 22:10 UTC

Return-Path: <resnick@episteme.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 186CD3A1259 for <gendispatch@ietfa.amsl.com>; Tue, 13 Apr 2021 15:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 hSXHgrioA8rz for <gendispatch@ietfa.amsl.com>; Tue, 13 Apr 2021 15:10:43 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AA9D3A1257 for <gendispatch@ietf.org>; Tue, 13 Apr 2021 15:10:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 0EBB8E0900B1; Tue, 13 Apr 2021 17:10:42 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NtQp6ANN8ugZ; Tue, 13 Apr 2021 17:10:40 -0500 (CDT)
Received: from [172.16.1.27] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id A8724E0900A8; Tue, 13 Apr 2021 17:10:40 -0500 (CDT)
From: Pete Resnick <resnick@episteme.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: gendispatch@ietf.org
Date: Tue, 13 Apr 2021 17:10:40 -0500
X-Mailer: MailMate (1.14r5786)
Message-ID: <96204CB3-C9E8-4EBB-BBB2-EB59E2F316F3@episteme.net>
In-Reply-To: <b946972c-99a8-5fab-43d9-894a6cc3a655@gmail.com>
References: <20210413200128.D5C3472D2739@ary.qy> <b946972c-99a8-5fab-43d9-894a6cc3a655@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; markup="markdown"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/OZfhjugWkkVQbV3V0coOMWn-mUQ>
Subject: Re: [Gendispatch] WG Review: Effective Terminology in IETF Documents (term)
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: Tue, 13 Apr 2021 22:10:48 -0000

[Removing ietf@ietf.org]

Was there a particular reason you copied GENDISPATCH on your message? 
Did you perhaps intend the terminology list?

pr

On 13 Apr 2021, at 16:53, Brian E Carpenter wrote:

> On 14-Apr-21 08:01, John Levine wrote:
>> It appears that Salz, Rich <rsalz@akamai.com> said:
>>> -=-=-=-=-=-
>>> I believe it is important for the IETF to say something that has the 
>>> force of IETF consensus behind it.  Instructions to the RFC Editor 
>>> have not, and I would
>>> be against doing so in this case because the lack of consensus makes 
>>> the editorial changes less well-justified.
>>>
>>> If the consensus is that we should not do this, I would be highly 
>>> disappointed, but I would accept it as a consensus decision.
>>
>> Language policing is not part of the RFC Editor's job.
>
> That may be true today, but when we have a new regime for the RFC 
> Series model it might change, or at least, this whole issue might 
> become part of the style guide.
>
>> If the IETF wants to set language standards, that is fine,
>
> s/standards/guidelines/
>
>> but it is up to the IETF itself to follow and if need be enforce 
>> those standards, not anyone else.
>
> I hope you would apply that statement to all RFC streams, not just the 
> IETF stream.
>
> Regards
>     Brian


-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best