Re: [Editorial Errata Reported] RFC8632 (5953)

Hi,

The original text is correct.  It is intended to examplify how the
severity can change multiple times over the lifecycle of an alarm.


/martin


RFC Errata System <[email protected]> wrote:
> The following errata report has been submitted for RFC8632,
> "A YANG Data Model for Alarm Management".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid5953
> 
> --------------------------------------
> Type: Editorial
> Reported by: Tetsuya Hasegawa <[email protected]>
> 
> Section: 3.5.1.
> 
> Original Text
> -------------
>    From a resource perspective, an alarm can, for example, have the
>    following lifecycle: raise, change severity, change severity, clear,
> 
> Corrected Text
> --------------
>    From a resource perspective, an alarm can, for example, have the
>    following lifecycle: raise, change severity, clear,
> 
> Notes
> -----
> 
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC8632 (draft-ietf-ccamp-alarm-module-09)
> --------------------------------------
> Title               : A YANG Data Model for Alarm Management
> Publication Date    : September 2019
> Author(s)           : S. Vallin, M. Bjorklund
> Category            : PROPOSED STANDARD
> Source              : Common Control and Measurement Plane
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG
> 

_______________________________________________
CCAMP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ccamp