Re: [Terminology] Do you intend to use draft-knodel-terminology as if it is the opinion of the IETF?

S Moonesamy <sm+ietf@elandsys.com> Mon, 15 November 2021 11:20 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: terminology@ietfa.amsl.com
Delivered-To: terminology@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 191A13A091E for <terminology@ietfa.amsl.com>; Mon, 15 Nov 2021 03:20:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 1GOOONQTUSDb for <terminology@ietfa.amsl.com>; Mon, 15 Nov 2021 03:19:58 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 79E6F3A0907 for <terminology@ietf.org>; Mon, 15 Nov 2021 03:19:58 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.42.135]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 1AFBJVKV000494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Nov 2021 03:19:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1636975183; x=1637061583; i=@elandsys.com; bh=zTUsiCY8FxyLk3ENIil2yTah5b9SeQyNxvyVJImxMOU=; h=Date:To:From:Subject:In-Reply-To:References; b=jDsIJzpg6cJowAXjcGBZiWzThbxzj4NMp3tA9vV9PABIX2g2l4ZF1cVRJFae4xc5n gcEgQB0BLWmwLWMl61UAVCQHcxo3miqCG+DztpXJ/5c8egYn7ZUTka08TJLGz/hZbu SiVw3rqvT3G9tNIPbnF7xxBdDV7gLJrEEKOvNrEc=
Message-Id: <6.2.5.6.2.20211115015507.0b245158@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 15 Nov 2021 03:19:08 -0800
To: Bron Gondwana <brong@fastmailteam.com>, terminology@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <e66519f4-2cec-469d-af65-856564bafd1f@beta.fastmail.com>
References: <ac78f557-00c5-48ff-8920-c13f5b7420a5@dogfood.fastmail.com> <e66519f4-2cec-469d-af65-856564bafd1f@beta.fastmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/g-H9B3lP17HZ9i1T50oDh-hWZII>
Subject: Re: [Terminology] Do you intend to use draft-knodel-terminology as if it is the opinion of the IETF?
X-BeenThere: terminology@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Effective Terminology in IETF Documents <terminology.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/terminology>, <mailto:terminology-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/terminology/>
List-Post: <mailto:terminology@ietf.org>
List-Help: <mailto:terminology-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/terminology>, <mailto:terminology-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Nov 2021 11:20:03 -0000

Hi Bron,

[removed authors of the draft and the ISE as recipients]

At 03:57 PM 14-11-2021, Bron Gondwana wrote:
>But to many outside the IETF, the difference between "Independent 
>Submission" and "Cast In Stone Internet Standard[tm]" is not at all 
>obvious, and the mere fact of having a RFC number lends gravitas to 
>the topic covered.  So publishing this one set of opinions as "an 
>RFC", and referencing said RFC to buttress debate outside the IETF, 
>would be a disingenuous and dishonest representation of the IETF's 
>name and reputation.

It makes life easier if a person is upfront about any potential 
conflicts.  I'll disclose that I am on the ISEB.

Many years ago, there was an attempt to shut down the Independent 
Stream.  I argued for keeping the Stream.  The argument, if from what 
I remember, was that it could be a yardstick to measure the success 
(or failure) of the Internet Standards Process.

I'll comment about the "disingenous and dishonest representation 
..."  Some participants stated that "the IETF is not the Internet 
police".  That is not accurate if an external publication is blocked 
to protect the IETF's name and reputation [1].  Adding to that, it is 
not appropriate for the external publication to publish an opinion 
which misrepresent the facts about the IETF.

Regards,
S. Moonesamy

1. Please do not read the sentence as a statement of support for 
publication of the draft.