Subject: alarmActiveState notification

From: Randy Presuhn <[email-masked]>
Date: Tue, 16 Apr 2002 17:58:33 -0700 (PDT)

Hi -

In draft-ietf-disman-alarm-mib-06.txt, the definition of the
alarmActiveState notification includes references to two
accessible-for-notify objects, alarmModelIndexVarbind and
alarmModelStateVarbind.  It seems to me that it would be
quite a bit simpler to remove these two from the OBJECTS
list, and replace them with alarmActiveModelPointer.

Similarly, in the definition of the alarmClearState
notification, alarmModelIndexVarbind could also replaced
with alarmActiveModelPointer.

This would allow us to get rid of two object definitions,
and all the varbinds in the OBJECTS clause would come from
the same row in the same table, simplifying implementation.

While we're on the topic of these two notifications, I
think that alarmActiveResourceId is not particularly useful
without alarmActiveContextName, alarmActiveEngineAddressType,
alarmActiveEngineAddress, and alarmActiveEngineID.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 [email-masked]  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------