Re: [CCAMP] Opsdir last call review of draft-ietf-ccamp-alarm-module-07

[Joe Clarke <[e-mail]>]

On 3/19/19 11:30, stefan vallin wrote:
> Hi!
> 
>> On 19 Mar 2019, at 16:23, Joe Clarke <[e-mail]
>> <mailto:[e-mail]>> wrote:
>>
>> Do you
>> envision a non-shelved alarm to periodically generate notifications
>> while active, or is it one-and-done?
> Oh yes, see
> 3.5.1.  Resource Alarm Life-Cycle
> 
>    From a resource perspective, an alarm can for example have the
>    following life-cycle: raise, change severity, change severity, clear,
>    being raised again etc.  All of these status changes can have 
>    different alarm texts generated by the instrumentation
> 
> 
> That is the purpose of having the resource and alarm-type as key
> As long as you do not purge (delete) the alarm it can change:
> * severity
> * alarm-text
> * is-cleared
> 
> Each of the generating a notification.
> 
> If that was your question….

Not exactly.  I saw the life-cycle stuff -- and this edge trigger makes
sense -- but I was asking that if the state is raise, will multiple
notifications be sent for raise (or could multiple, periodic
notifications be sent)?  For example, while status is "raise" and
without any other change, send a notification every five minutes.

And now that you call out this text, "change severity" is listed twice :-).

Joe