RE: Final Closure on Entity State MIB Issues

> #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

   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 ?

> #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).



Bert