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> Thu, 18 November 2021 06:49 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 4900D3A08AF for <terminology@ietfa.amsl.com>; Wed, 17 Nov 2021 22:49:43 -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 UDv8g8SGL8TO for <terminology@ietfa.amsl.com>; Wed, 17 Nov 2021 22:49:38 -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 C66903A07FF for <terminology@ietf.org>; Wed, 17 Nov 2021 22:49:29 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.61.170]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 1AI6mwMO025520 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2021 22:49:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1637218153; x=1637304553; i=@elandsys.com; bh=TBdLjTvpSYcaks9ReuAbqfs3QH40xDYsf8IS6EqD0E4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vbNvwkHnKlgUBO1YhsfPc920twi+c6z2z2H7oyPeWWOmHI7wtgX6U5K7Ayjq5YAm8 h6RvEYwRxxQr8n8V/Gj08DDSsfb++HOXi0+4NszOV14wHb5RWwcl9eeXOjCHHzHxMe x5Ofu30a3UdyStyeFGUXE2Ig2o1m34JC6t7fsoe0=
Message-Id: <6.2.5.6.2.20211117215308.0b940840@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 17 Nov 2021 22:25:23 -0800
To: Jim Fenton <fenton@bluepopcorn.net>, terminology@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Mallory Knodel <mknodel@cdt.org>, mail@nielstenoever.net
In-Reply-To: <80FBDFDC-8CAA-4311-8D10-C236BFDAD600@bluepopcorn.net>
References: <ac78f557-00c5-48ff-8920-c13f5b7420a5@dogfood.fastmail.com> <e66519f4-2cec-469d-af65-856564bafd1f@beta.fastmail.com> <80FBDFDC-8CAA-4311-8D10-C236BFDAD600@bluepopcorn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/w-XlD8yGdtEGScuJwDgha-1Mu2w>
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: Thu, 18 Nov 2021 06:49:48 -0000

Hi Jim,
At 03:11 PM 17-11-2021, Jim Fenton wrote:
>There is considerable potential for this document to be viewed as an 
>IETF statement. I learned of this document's existence through a 
>reference in an earlier revision of the NIST Technical Series 
>Publications Author Instructions to an early revision of 
>draft-knodel-terminology citing it as "IETF". This has now been 
>replaced with a reference to https://github.com/ietf/terminology 
>(which I also have questions about with respect to IETF consensus), 
>but it shows how documents of this sort can be misconstrued as 
>coming from IETF. The potential for this is amplified by giving the 
>document an RFC number.

Thanks for raising the above issue.  I don't think that it is a good 
idea to apply a different "rule" for the github.com repository.  The 
repository does not represent consensus.  It can also be misconstrued 
as the IETF's position on the question of terminology.

There is the following sentence in the Abstract of -07: "This 
document represents the opinion of the authors and does not have IETF 
consensus."  It is unusual to see an author including such a 
statement in his/her draft.

Several IETF participants supported the draft, if my reading is 
correct.  It is not clear whether those participants reviewed the 
draft as there isn't any acknowledgement in the draft.

Now, I understand why you asked whether the reviews would be publicly 
accessible.

Regards,
S. Moonesamy