IETF Logo Mail Archive

Re: [Terminology] Recent posts to the terminology mailing list

S Moonesamy <sm+ietf@elandsys.com> Sun, 07 November 2021 07:43 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 789693A10F2 for <terminology@ietfa.amsl.com>; Sun, 7 Nov 2021 00:43:53 -0700 (PDT)
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 WHff_UVmFC3h for <terminology@ietfa.amsl.com>; Sun, 7 Nov 2021 00:43:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 965D23A10F1 for <terminology@ietf.org>; Sun, 7 Nov 2021 00:43:48 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.9.35]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 1A77hUf5010757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Nov 2021 00:43:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1636271021; x=1636357421; i=@elandsys.com; bh=7+5icjk9SZl7dsUIP2Z9rY9d3RGnAB2/2bsKRWwfm+0=; h=Date:To:From:Subject:In-Reply-To:References; b=j+9Gbsjwm3QM04qDtz8oe0ctsU5YKxMCooy21TUhAb6E4w4Tn+yYKkkXGS9+QATZB qNRy0nsv87yuIxCR+rW97QQ8KgoiIQ6WPuL64psmI2C2wacMsl+y6PBOMJyVGgbaav NpeRJgPJ6IKgO3oGTNyZu5H/YFQV7rRSww+YoKMU=
Message-Id: <6.2.5.6.2.20211107002122.13316280@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 07 Nov 2021 00:41:48 -0700
To: Nick Doty <npdoty@ischool.berkeley.edu>, terminology@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CAFfrZstPj8ZmQNrv5AG_u3soHsu0t=rKzc8OisFwpWtgz3GAhw@mail.g mail.com>
References: <BY5PR11MB419686515616F100D00EA0AFB58D9@BY5PR11MB4196.namprd11.prod.outlook.com> <CAFfrZstPj8ZmQNrv5AG_u3soHsu0t=rKzc8OisFwpWtgz3GAhw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/GnCZDQp0lUT5beVFIOYPzbsamxA>
Subject: Re: [Terminology] Recent posts to the terminology mailing list
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: Sun, 07 Nov 2021 07:43:54 -0000

Hi Nick,
At 02:02 PM 05-11-2021, Nick Doty wrote:
>I don't have strong feelings either way, but I'm fine with keeping 
>the list open for discussion of terminology questions, the IESG 
>statement and how to make use of the NIST report. As I recall, it 
>was used for that regarding NTP and interactions with IEEE, which 
>seemed helpful.

I took a quick look at the thread.  Ms O'Donoghue was one of the 
working group chairs in which the draft was discussed.  Mr Levine is 
the Temporary RFC Series Editor.  The other person who commented on 
the thread regularly participates in discussions on several other 
IETF mailing lists.  The same guidance could have been provided by 
those participants if this mailing list did not exist.

Regards,
S. Moonesamy

v2.23.0 | Report a Bug | By Email