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

"Sharon Chisholm" <schishol@nortelnetworks.com> Mon, 29 March 2004 15:31 UTC

Received: from optimus.ietf.org (optimus.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08096 for <entmib-archive@lists.ietf.org>; Mon, 29 Mar 2004 10:31:30 -0500 (EST)
Received: from localhost.localdomain ([] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B7yj8-00081N-Nk; Mon, 29 Mar 2004 10:31:02 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B7yiY-0007yj-SN for entmib@optimus.ietf.org; Mon, 29 Mar 2004 10:30:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08055 for <entmib@ietf.org>; Mon, 29 Mar 2004 10:30:22 -0500 (EST)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 1B7yiW-0003aD-00 for entmib@ietf.org; Mon, 29 Mar 2004 10:30:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B7yhZ-0003Px-00 for entmib@ietf.org; Mon, 29 Mar 2004 10:29:26 -0500
Received: from zcars04f.nortelnetworks.com ([]) by ietf-mx with esmtp (Exim 4.12) id 1B7ygf-0003B6-00 for entmib@ietf.org; Mon, 29 Mar 2004 10:28:29 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com []) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2TFRvA11499 for <entmib@ietf.org>; Mon, 29 Mar 2004 10:27:57 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <GXT6L3F5>; Mon, 29 Mar 2004 10:27:58 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340AA423AB@zcard0ka.ca.nortel.com>
From: Sharon Chisholm <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Mon, 29 Mar 2004 10:27:51 -0500
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
Subject: [Entmib] #322 - Textual Convention Names (Prefix)
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>


I'm not sure if consensus is fully formed yet, but I wanted to test a view
that it seems to be leaning  in the direction of creating a separate MIB
within this ID to house to textual conventions who's prefix we have not yet
determined? Is that were people are or is more discussion required?

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 Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

Entmib mailing list