Re: Event classes

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "Balazs Lengyel" <balazs.lengyel@ericsson.com>
> To: "Andy Bierman" <ietf@andybierman.com>
> Cc: "Netconf (E-mail)" <netconf@ops.ietf.org>
> Sent: Monday, May 29, 2006 1:34 AM
> Subject: Re: Event classes
...
> State is a good choice but there is a more general issue hidden here.
> 
> State events can also represent a fault. E.g. For threshold-crossing: memory-usage more 
> then 20% is just a state event. Memory usage more then 99.9% is a critical fault/alarm as 
> at this point we can easily have a crash. Where do we put such events? Shall we
> - allow such events to jump from state to fault depending on the seriousness of the situation
> - allow some notifications to belong to more then one event class
> - leave it to the application developer
...

I think that syntactic needs, rather than semantic distinctions,
will be most useful in characterizing event classes at the level
of a data model.   Decisions about "seriousness" are in the
eye of the beholder, and may depend on the context in which
they occur.

Randy


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>