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

"Sharon Chisholm" <schishol@nortelnetworks.com> Tue, 23 March 2004 17:26 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 MAA13450 for <entmib-archive@lists.ietf.org>; Tue, 23 Mar 2004 12:26:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B5pfE-0004mx-B9; Tue, 23 Mar 2004 12:26:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B5peW-0004Y5-FH for entmib@optimus.ietf.org; Tue, 23 Mar 2004 12:25:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13421 for <entmib@ietf.org>; Tue, 23 Mar 2004 12:25:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B5peU-000317-00 for entmib@ietf.org; Tue, 23 Mar 2004 12:25:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B5pdS-0002zS-00 for entmib@ietf.org; Tue, 23 Mar 2004 12:24:18 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1B5pcT-0002vd-00 for entmib@ietf.org; Tue, 23 Mar 2004 12:23:17 -0500
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 i2NHMdF21176 for <entmib@ietf.org>; Tue, 23 Mar 2004 12:22:39 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <GXT6JALN>; Tue, 23 Mar 2004 12:22:39 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9677EB@zcard0ka.ca.nortel.com>
From: Sharon Chisholm <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues
Date: Tue, 23 Mar 2004 12:22:28 -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
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>

Comments inline

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Tuesday, March 23, 2004 10:13 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues

<clip>

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

   ItuXxxx
   
or
   UtuX731Xxxx

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 ?

Sharon> Except we have made a couple of modifications to the states. I think
we would have to undo these to call them OSI or ITU states.

> #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
1.3.6.1.2.1.xx  entityStateMIB  [ENTITY-STATE-MIB]: module-identity
1.3.6.1.2.1.xx.0  entStateNotifications  [ENTITY-STATE-MIB]:
oid-value-assignment
1.3.6.1.2.1.xx.0.1  entStateOperEnabled  [ENTITY-STATE-MIB]:
notification-type
1.3.6.1.2.1.xx.0.2  entStateOperDisabled  [ENTITY-STATE-MIB]:
notification-type
1.3.6.1.2.1.xx.1  entStateObjects  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.1.1  entStateTable  [ENTITY-STATE-MIB]: table-object-type
1.3.6.1.2.1.xx.1.1.1  entStateEntry  [ENTITY-STATE-MIB]: row-object-type
1.3.6.1.2.1.xx.1.1.1.1  entStateLastChanged  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.2  entStateAdmin  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.3  entStateOper  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.4  entStateUsage  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.5  entStateAlarm  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.6  entStateStandby  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.3  entStateConformance  [ENTITY-STATE-MIB]:
oid-value-assignment
1.3.6.1.2.1.xx.3.1  entStateCompliances  [ENTITY-STATE-MIB]:
oid-value-assignment
1.3.6.1.2.1.xx.3.1.1  entStateCompliance  [ENTITY-STATE-MIB]:
module-compliance
1.3.6.1.2.1.xx.3.2  entStateGroups  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.3.2.1  entStateGroup  [ENTITY-STATE-MIB]: object-group
1.3.6.1.2.1.xx.3.2.2  entStateNotificationsGroup  [ENTITY-STATE-MIB]:
notification-group
**end of oid tree**

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

Sharon> This sounds like a different problem then what he is saying.

Sharon

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