RE: [Entmib] Final Closure on Entity State MIB Issues

"Wijnen, Bert (Bert)" <> Tue, 23 March 2004 15:17 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id KAA02428 for <>; Tue, 23 Mar 2004 10:17:28 -0500 (EST)
Received: from localhost.localdomain ([] by with esmtp (Exim 4.20) id 1B5neH-0003Kq-2H; Tue, 23 Mar 2004 10:17:01 -0500
Received: from ([] by with esmtp (Exim 4.20) id 1B5ndc-0003CB-0g for; Tue, 23 Mar 2004 10:16:20 -0500
Received: from ietf-mx ( []) by (8.9.1a/8.9.1a) with ESMTP id KAA02300 for <>; Tue, 23 Mar 2004 10:16:15 -0500 (EST)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 1B5ndY-0000Ih-00 for; Tue, 23 Mar 2004 10:16:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B5ncb-0000Bb-00 for; Tue, 23 Mar 2004 10:15:18 -0500
Received: from ([] by ietf-mx with esmtp (Exim 4.12) id 1B5nbm-0007lw-00 for; Tue, 23 Mar 2004 10:14:26 -0500
Received: from ( []) by (Switch-2.2.8/Switch-2.2.8) with ESMTP id i2NFDH215618 for <>; Tue, 23 Mar 2004 09:13:26 -0600 (CST)
Received: by with Internet Mail Service (5.5.2657.72) id <1699ZYFP>; Tue, 23 Mar 2004 16:13:15 +0100
Message-ID: <>
From: "Wijnen, Bert (Bert)" <>
To: Sharon Chisholm <>,
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues
Date: Tue, 23 Mar 2004 16:13:13 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <>, <>
List-Id: IETF Entity MIB WG <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

> #322: Textual Convention Names (Prefix)
> 	I think the TC names should be prefixed.
> Sharon> Ok. I think we need to step back a level on this one. 
> We seemed to
> have had agreement on the list that if the TCs were intended to be not
> specific to Entities, then they should not have the prefix 
> but if they were
> they should. So, I suspect we are disagreeing on whether these TCs are
> specific to Entities. I certainly never intended them to be 
> and went out of
> my way to ensure they weren't. Is there something in their 
> definition that
> leads you to believe they are limited in their application to 
> Entities?

It seems to me that your TCs shoudl be prefixed with something aka


That is what they claim to represent.
And having said that... should it be a separate ITU module (i.e. have ITU
in the name and TC-MIB as a suffix) ??
Maybe to heavy ?

> #325:
> 	The figures in the discussion of this issue are wrong as
> 	xxxCompliances(1) and xxxGroups(2) are typically registered
> 	below xxxConformance(2).
> Sharon> This is from the MIB Review Guidelines. 
I think Juergen meant to say that you are using xxxConformance(3)
while you should be using xxxConformance(2).

Your OIDs look like:
OID tree  entityStateMIB  [ENTITY-STATE-MIB]: module-identity  entStateNotifications  [ENTITY-STATE-MIB]: oid-value-assignment  entStateOperEnabled  [ENTITY-STATE-MIB]: notification-type  entStateOperDisabled  [ENTITY-STATE-MIB]: notification-type  entStateObjects  [ENTITY-STATE-MIB]: oid-value-assignment  entStateTable  [ENTITY-STATE-MIB]: table-object-type  entStateEntry  [ENTITY-STATE-MIB]: row-object-type  entStateLastChanged  [ENTITY-STATE-MIB]: columnar-object-type  entStateAdmin  [ENTITY-STATE-MIB]: columnar-object-type  entStateOper  [ENTITY-STATE-MIB]: columnar-object-type  entStateUsage  [ENTITY-STATE-MIB]: columnar-object-type  entStateAlarm  [ENTITY-STATE-MIB]: columnar-object-type  entStateStandby  [ENTITY-STATE-MIB]: columnar-object-type  entStateConformance  [ENTITY-STATE-MIB]: oid-value-assignment  entStateCompliances  [ENTITY-STATE-MIB]: oid-value-assignment  entStateCompliance  [ENTITY-STATE-MIB]: module-compliance  entStateGroups  [ENTITY-STATE-MIB]: oid-value-assignment  entStateGroup  [ENTITY-STATE-MIB]: object-group  entStateNotificationsGroup  [ENTITY-STATE-MIB]: notification-group
**end of oid tree**

And so was skipped (for as far as we can tell no good reason).


Entmib mailing list