Re: Entity State MIB Next Steps

Hi
 a Minor Suggestion:

Instead of having these OID definitions:

-- Notifications

   entStateTraps      OBJECT IDENTIFIER ::= { entityStateMIB 2 }
   entStateTrapPrefix OBJECT IDENTIFIER ::= { entStateTraps 0 }


We can have
 entStateNotifs OBJECT IDENTIFIER ::= { entityStateMIB 0 }
 
and use 'entStateNotifs' in the corresponding NOTIFICATION-TYPE

Reason we would like to avoid name 'Traps' is: Latest RFCs refer them
as Notifications


Subra



Margaret Wasserman wrote:

>
> Now that the newest version of the Entity State MIB is available,
> the WG has a decision to make.  In my opinion, we have two
> choices:
>
> (1) We decide that the structure and objects defined in the
> current draft are acceptable, and we send the current draft
> to WG Last Call in order to identify and resolve final
> issues.
>
> (2) We decide that we want to change the structure or objects
> defined in this MIB to make it simpler or more functional.
>
> I would appreciate it if people would respond to this message
> with their opinions, so that I can attempt to judge the consensus
> of the WG on this issue.
>
> Thanks,
> Margaret
>
>
> _______________________________________________
> Entmib mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/entmib
>