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

stefan vallin <stefan@wallan.se> Wed, 15 January 2020 16:38 UTC

Return-Path: <stefan@wallan.se>
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 0816012087B for <ccamp@ietfa.amsl.com>; Wed, 15 Jan 2020 08:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=wallan-se.20150623.gappssmtp.com
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 rMQJC9aE9zrx for <ccamp@ietfa.amsl.com>; Wed, 15 Jan 2020 08:38:51 -0800 (PST)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B49A112085B for <ccamp@ietf.org>; Wed, 15 Jan 2020 08:38:50 -0800 (PST)
Received: by mail-lj1-x22f.google.com with SMTP id r19so19297498ljg.3 for <ccamp@ietf.org>; Wed, 15 Jan 2020 08:38:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wallan-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PLVmx3a4WenoU+lcCqEqZ7v/0rGWWXAZGyctNO+F0Lo=; b=La+U/DgUgG+rSKrqhkRwoJxTgfsMQM48vUygZeHDKirFhSKN4UYxocslS/L0cm12mn OAgXRS3bx2TkWxZmYXGndzP5FSVtn2oqHy3TRD/VHT/EOuVq97wl5GFYbWS79uAKZibc VP6spJGutttYFgPVIQl1zkA5ejdF6MSmkiR8gWmJP0mRNe7IlRNR0a6gZhzvHK5nIrG0 3iDNGieicPEFFwrRAUqtdImyu+pjyZ8SvLhYdAOYY4FglAk5XhrrIGPmhUQ2zxkaRHZ6 Ky0hWKHApfRdpK5Ta8iaVyQ7U0WlRjmF1vaFlbEYgLvKUwg8ic1IamFMdaU4cblDMFsa lxjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PLVmx3a4WenoU+lcCqEqZ7v/0rGWWXAZGyctNO+F0Lo=; b=dCwx8tGcsSuoZF5PmTs/mgCRtDRBjipenfnHhd7vU4uX9L1aCBeRu45CcPLzrhmloe ftJoNzkL4mAdwq0dWie8tI8tnMoNpilvYYf1lM7gjpKKHlNufYpEgXcVwv4aPwd2KiOf KW9C11QGe4R6PmHkcbYYTUfIB37nFeQQDxS0vLOF195ZoMdOZAkJL75AVBistFVNG61W JtOsQyrACdb5IK+05FwOxoGaCueiuHF4Q19icbF9Qo6sBMY7Ck5k44uxqsZ2Zz6sRGRJ Zks9MJQbqp9YbkSYOnSPvfuRlJT232/bdNiBulYgFUQr/5aBAuSnPRZG9M2Wnew05Ecm iwQg==
X-Gm-Message-State: APjAAAUCnFVMJFszQyNGaKZuPfiSFk7XBolx+KPFuamiX5DWR4CXfQnO 8pnwed7R6SuajC9qRQXltTfPbA==
X-Google-Smtp-Source: APXvYqx8aKfedVLA931l82COS1852O4kwA+D0Dhk+pMTuOjdKzS35gRr1p1sGdp0xtkAlMaMv1cGlQ==
X-Received: by 2002:a2e:b017:: with SMTP id y23mr2432854ljk.229.1579106328727; Wed, 15 Jan 2020 08:38:48 -0800 (PST)
Received: from [192.168.72.11] (h95-155-237-105.cust.a3fiber.se. [95.155.237.105]) by smtp.gmail.com with ESMTPSA id i197sm9254238lfi.56.2020.01.15.08.38.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Jan 2020 08:38:48 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: stefan vallin <stefan@wallan.se>
In-Reply-To: <20200105.205558.329921899573294327.mbj@tail-f.com>
Date: Wed, 15 Jan 2020 17:38:43 +0100
Cc: "BRUNGARD, DEBORAH A" <db3546@att.com>, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, Fatai Zhang <zhangfatai@huawei.com>, te.hasegawa2@gmail.com, "CCAMP (ccamp@ietf.org)" <ccamp@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <026D688E-1074-442A-90C0-775DA7095416@wallan.se>
References: <20191231024914.928B7F4073D@rfc-editor.org> <20200105.205558.329921899573294327.mbj@tail-f.com>
To: Martin Bjorklund <mbj@tail-f.com>, rfc-editor@rfc-editor.org
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/nFd791TpFC2q7GPEYqHvgB_Xsho>
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: Wed, 15 Jan 2020 16:38:56 -0000

Hi,
Agree with Martin,  the RFC text is correct.
/stefan


> On 5 Jan 2020, at 20:55, Martin Bjorklund <mbj@tail-f.com> wrote:
> 
> 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
>>