IETF Logo Mail Archive

Re: [CCAMP] I-D Action: draft-ietf-ccamp-alarm-module-06.txt

NICK HANCOCK <nick.hancock@adtran.com> Mon, 03 December 2018 11:16 UTC

Return-Path: <nick.hancock@adtran.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 A3E45130E4B for <ccamp@ietfa.amsl.com>; Mon, 3 Dec 2018 03:16:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 TmbsI-ojjFKc for <ccamp@ietfa.amsl.com>; Mon, 3 Dec 2018 03:16:23 -0800 (PST)
Received: from us-smtp-delivery-128.mimecast.com (us-smtp-delivery-128.mimecast.com [63.128.21.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DEED128DFD for <ccamp@ietf.org>; Mon, 3 Dec 2018 03:16:23 -0800 (PST)
Received: from ex-hc3.corp.adtran.com (ex-hc2.adtran.com [76.164.174.82]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-270-5-_s0-AOMvy9MN3XQUn8MQ-1; Mon, 03 Dec 2018 06:16:20 -0500
Received: from ex-mb3.corp.adtran.com ([fe80::60aa:f95:ad49:a0f1]) by ex-hc3.corp.adtran.com ([fe80::3892:20fa:600f:75c6%15]) with mapi id 14.03.0382.000; Mon, 3 Dec 2018 05:16:19 -0600
From: NICK HANCOCK <nick.hancock@adtran.com>
To: "ccamp@ietf.org" <ccamp@ietf.org>, "stefan vallin (stefan@wallan.se)" <stefan@wallan.se>
Thread-Topic: [CCAMP] I-D Action: draft-ietf-ccamp-alarm-module-06.txt
Thread-Index: AQHUgjfG1kmNoVTdvUexPLUNs8DHYqVs3uww
Date: Mon, 03 Dec 2018 11:16:17 +0000
Message-ID: <BD6D193629F47C479266C0985F16AAC7011EA39876@ex-mb3.corp.adtran.com>
References: <154287290784.5405.11527708644353771052@ietfa.amsl.com>
In-Reply-To: <154287290784.5405.11527708644353771052@ietfa.amsl.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0FEVFJBTiIsImlkIjoiYmQ5ODhkNTUtNjY0NC00ZThiLTkyMjAtMmE4NmY1NzY0YzYzIiwicHJvcHMiOlt7Im4iOiJDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiR0IifV19LHsibiI6IlF1ZXN0aW9uMSIsInZhbHMiOltdfSx7Im4iOiJRdWVzdGlvbjIiLCJ2YWxzIjpbXX0seyJuIjoiUXVlc3Rpb24zIiwidmFscyI6W119XX0sIlN1YmplY3RMYWJlbHMiOltdLCJUTUNWZXJzaW9uIjoiMTcuMi4xMS4wIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImFLXC9ReGNnRG9DTk9uMnMxYzZNMmR2TCtUeE12NHdoV1dnN3pBR0RPNTNMYzlqNkFCNGtrdmNYWEd0N2I4c21nIn0=
x-originating-ip: [172.20.61.181]
MIME-Version: 1.0
X-MC-Unique: 5-_s0-AOMvy9MN3XQUn8MQ-1
Content-Type: multipart/alternative; boundary="_000_BD6D193629F47C479266C0985F16AAC7011EA39876exmb3corpadtr_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/i8ve8hZDXvbdpFoYgviD1ff6INU>
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-alarm-module-06.txt
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: Mon, 03 Dec 2018 11:16:27 -0000

Hi Stefan,

I am very happy with the progress of the YANG Alarm Module and fully support it.

There is, however, some uncertainty regarding how alarm severities are to be listed within the alarm inventory as a result of the configuration of alarm profiles that modify the alarm severity of a given alarm type for a specific set of resources only.

Since the alarm inventory is not keyed by resource, how can the modified alarm severity for the given subset of resources be unambiguously displayed in the alarm inventory?

Best regards
Nick


From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Thursday, November 22, 2018 8:48 AM
To: i-d-announce@ietf.org
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action: draft-ietf-ccamp-alarm-module-06.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Control and Measurement Plane WG of the IETF.

Title : YANG Alarm Module
Authors : Stefan Vallin
Martin Bjorklund
Filename : draft-ietf-ccamp-alarm-module-06.txt
Pages : 79
Date : 2018-11-21

Abstract:
This document defines a YANG module for alarm management. It
includes functions for alarm list management, alarm shelving and
notifications to inform management systems. There are also
operations to manage the operator state of an alarm and
administrative alarm procedures. The module carefully maps to
relevant alarm standards.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-ccamp-alarm-module/<https://datatracker.ietf.org/doc/draft-ietf-ccamp-alarm-module/>

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-ccamp-alarm-module-06<https://tools.ietf.org/html/draft-ietf-ccamp-alarm-module-06>
https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-alarm-module-06<https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-alarm-module-06>

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-alarm-module-06<https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-alarm-module-06>


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/<ftp://ftp.ietf.org/internet-drafts/>

_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp<https://www.ietf.org/mailman/listinfo/ccamp>

v2.23.0 | Report a Bug | By Email