Re: Some editorial proposals fordraft-ietf-disman-event-mib-v2-04.txt

Hi -

(as a technical contributor)

> From: "Benoit Claise" <[email protected]>
> To: "Disman (E-mail)" <[email protected]>
> Sent: Friday, June 03, 2005 2:00 PM
> Subject: [Disman] Some editorial proposals fordraft-ietf-disman-event-mib-v2-04.txt
...
> 1. Section 3. Relationship to Other MIBs
>
>    "Event MIB triggers maintain the RMON handling of thresholds and add the concept
>    of booleans."
>
> I would propose:
>    "Event MIB triggers maintain the RMON handling of thresholds and add the concept
>    of booleans and existence."
> AFAIK, RMON doesn't have the concept of "existence"

I don't think we need this.
See the first paragraph of RFC 2021's definition of TimeFilter.

> 2. Section 4.  MIB Sections
>
>    "The MIB has four sections: triggers, objects, events, and
>    notifications.  Triggers define the conditions that lead to events.
>    Events may cause notifications."
>
> I would propose:
>    "The MIB has four sections: triggers, objects, events, and
>    notifications.  Triggers define the conditions that lead to events.
>    Events may cause notifications and/or may set a MIB object."

Ok, but "and/or" is an abomination.  Also, why is "object" in the singular while
"notifications" is plural?

> 3. The MIB is full of mte*. I think the meaning of it is somehow hidden in the MIB:
> -- Management Triggered Event (MTE) objects
>
> I would propose to modify the MIB description from :
>     DESCRIPTION
>      "The MIB module for defining event triggers and actions
>      for network management purposes.
> To:
>     DESCRIPTION
>      "The MIB module for defining Managed Triggered Event (MTE) and actions
>      for network management purposes.

This seems helpful.

>
> Any objections?
>
> Regards, Benoit.

Randy