Re: [CCAMP] [Editorial Errata Reported] RFC8632 (5953)

Martin Bjorklund <mbj@tail-f.com> Sun, 05 January 2020 19:56 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7091200B1 for <ccamp@ietfa.amsl.com>; Sun, 5 Jan 2020 11:56:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LYznlsQ6Xu5D for <ccamp@ietfa.amsl.com>; Sun, 5 Jan 2020 11:56:02 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id A85D5120088 for <ccamp@ietf.org>; Sun, 5 Jan 2020 11:56:02 -0800 (PST)
Received: from localhost (h-4-44.A165.priv.bahnhof.se [158.174.4.44]) by mail.tail-f.com (Postfix) with ESMTPSA id 4832D1AE0385; Sun, 5 Jan 2020 20:55:58 +0100 (CET)
Date: Sun, 05 Jan 2020 20:55:58 +0100 (CET)
Message-Id: <20200105.205558.329921899573294327.mbj@tail-f.com>
To: rfc-editor@rfc-editor.org
Cc: stefan@wallan.se, db3546@att.com, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, daniele.ceccarelli@ericsson.com, zhangfatai@huawei.com, te.hasegawa2@gmail.com, ccamp@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20191231024914.928B7F4073D@rfc-editor.org>
References: <20191231024914.928B7F4073D@rfc-editor.org>
X-Mailer: Mew version 6.8 on Emacs 25.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/yOPI-0uBACghXoFfz-UR70m0mlg>
Subject: Re: [CCAMP] [Editorial Errata Reported] RFC8632 (5953)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jan 2020 19:56:05 -0000

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 <rfc-editor@rfc-editor.org> 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 <te.hasegawa2@gmail.com>
> 
> 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
>