RE: [Entmib] #322 - Textual Convention Names (Prefix)

"Sharon Chisholm" <schishol@nortelnetworks.com> Mon, 12 April 2004 20:14 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11875 for <entmib-archive@lists.ietf.org>; Mon, 12 Apr 2004 16:14:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BD7of-0004fH-FL; Mon, 12 Apr 2004 16:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BD7oA-0004a6-0F for entmib@optimus.ietf.org; Mon, 12 Apr 2004 16:13:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11795 for <entmib@ietf.org>; Mon, 12 Apr 2004 16:13:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BD7o6-00065g-00 for entmib@ietf.org; Mon, 12 Apr 2004 16:13:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BD7Yi-0004fl-00 for entmib@ietf.org; Mon, 12 Apr 2004 15:57:32 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1BD7RP-0003LV-00 for entmib@ietf.org; Mon, 12 Apr 2004 15:49:59 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i3CJnLV00218 for <entmib@ietf.org>; Mon, 12 Apr 2004 15:49:22 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <GXT6RBMN>; Mon, 12 Apr 2004 15:49:22 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD340ACD5D06@zcard0ka.ca.nortel.com>
From: Sharon Chisholm <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] #322 - Textual Convention Names (Prefix)
Date: Mon, 12 Apr 2004 15:49:12 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Post: <mailto:entmib@ietf.org>
List-Help: <mailto:entmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=subscribe>

hi

<clip> <Sharon>
> I think the term 'Entity' is too limiting if we agree we are going for 
> a more generic set of TCs. It occurs to be that we use the term 
> 'resource' in the Alarm MIB when we introduced the concept of a 
> 'ResourceId' as well as within the description clauses of the TCs in 
> this MIB. Would a prefix of 'ResourceState' work? </Sharon>

<randy>
I'd strongly prefer "EntityState" as a prefix.  The word "entity" is just
the college and sci-fi equivalent of "thingie", so I don't see how it would
be limiting.

</Randy>

I think because of the use we've made of it, it has morphed somewhat from
its generic use into being more specific to physical devices and logical
representations of multiple physical devices. If others don't feel using the
entity prefix will limit how people consider using the textual conventions,
then I can live with it. I just think that resource comes with less baggage
in the SNMP space.

Sharon

_______________________________________________
Entmib mailing list
Entmib@ietf.org
https://www1.ietf.org/mailman/listinfo/entmib