Subject: RE: [Disman] alarmModelRowStatus

From: "Sharon Chisholm" <[email-masked]>
Date: Wed, 8 Oct 2003 14:51:04 -0400

hi

The following is the proposed resolution to Randy-49. Assuming no objection,
this item will be considered closed conditional on the proposed edit being
done.

Add the following text to the description of alarmModelRowStatus:

As all read-create objects in this table have a DEFVAL clause, there is no
requirement that any object be explicitly set before this row can become
active. Note that a row consisting only of default values is not very
meaningful."

Sharon

-----Original Message-----
From: Randy Presuhn [mailto:[email-masked]] 
Sent: Friday, October 03, 2003 10:40 PM
To: Disman (E-mail)
Subject: Re: [Disman] alarmModelRowStatus

Hi -

> From: "Sharon Chisholm" <[email-masked]>
> To: "Disman (E-mail)" <[email-masked]>
> Cc: "Romascanu, Dan (Dan)" <[email-masked]>; "Randy Presuhn" 
> <[email-masked]>
> Sent: Friday, October 03, 2003 1:10 PM
> Subject: RE: [Disman] alarmModelRowStatus
...
> We have a proposed resolution to Randy-49 - since all objects in the 
> table have default values, no further changes are required.
>
> Objections?
...

Yes.  As MIB reviewer, I must point out yet again that the
MIB review guidelines require us to specify "which columnar objects (if any)
have to be set."  Dan's comments (or something to similar
effect) need to be reflected in the DESCRIPTION.

Randy