IETF Logo Mail Archive

[CCAMP] Comments on draft-ietf-ccamp-alarm-module-01 / shelf-name

NICK HANCOCK <nick.hancock@adtran.com> Tue, 27 February 2018 16:33 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 D3D1212DB6C for <ccamp@ietfa.amsl.com>; Tue, 27 Feb 2018 08:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.199
X-Spam-Level:
X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 OQ8bA-rPHdK7 for <ccamp@ietfa.amsl.com>; Tue, 27 Feb 2018 08:33:04 -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 013AA124217 for <ccamp@ietf.org>; Tue, 27 Feb 2018 08:33:03 -0800 (PST)
Received: from ex-hc1.corp.adtran.com (ex-hc1.adtran.com [76.164.174.81]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-190-rcpY1bz6Neax4uXQEUW6fQ-8; Tue, 27 Feb 2018 11:33:01 -0500
Received: from ex-mb1.corp.adtran.com ([fe80::51a3:972d:5f16:9952]) by ex-hc1.corp.adtran.com ([fe80::a43f:7ea6:7688:37b%13]) with mapi id 14.03.0382.000; Tue, 27 Feb 2018 10:28:48 -0600
From: NICK HANCOCK <nick.hancock@adtran.com>
To: "stefan vallin (stefan@wallan.se)" <stefan@wallan.se>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: Comments on draft-ietf-ccamp-alarm-module-01 / shelf-name
Thread-Index: AdOv4ZHjS3QaWGm9S4SStM7u/SFCng==
Date: Tue, 27 Feb 2018 16:28:47 +0000
Message-ID: <BD6D193629F47C479266C0985F16AAC7F06CBF69@ex-mb1.corp.adtran.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0FEVFJBTiIsImlkIjoiNDQyNTdmMTItYzUzNC00NGRlLTljZmMtMDllMzhkMTY1MTNjIiwicHJvcHMiOlt7Im4iOiJDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiUCJ9XX0seyJuIjoiUXVlc3Rpb24xIiwidmFscyI6W119LHsibiI6IlF1ZXN0aW9uMiIsInZhbHMiOltdfSx7Im4iOiJRdWVzdGlvbjMiLCJ2YWxzIjpbXX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNy4yLjExLjAiLCJUcnVzdGVkTGFiZWxIYXNoIjoidlJTYVNCT0ZBSVRwNVlKWGVIeUFjQUtiaU1PQzdYZ0RONEo5c0ZPWnNvMUpSYlBVM1lmc0hOKzNCTDcxVHVcL3AifQ==
x-originating-ip: [172.20.61.36]
MIME-Version: 1.0
X-MC-Unique: rcpY1bz6Neax4uXQEUW6fQ-8
Content-Type: multipart/alternative; boundary="_000_BD6D193629F47C479266C0985F16AAC7F06CBF69exmb1corpadtran_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/o1sQsiSJk20sOS_R1FspeZvEqBQ>
Subject: [CCAMP] Comments on draft-ietf-ccamp-alarm-module-01 / shelf-name
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 27 Feb 2018 16:33:06 -0000

Hi Stefan,

In the module 'ietf-alarms@2018-02-01' included in draft-ietf-ccamp-alarm-module-01, the leaf 'shelf-name' was added to the list 'shelved-alarm' to reference the entry in the list 'shelf' that caused the alarm to be shelved.
However, since it is possible to define multiple shelfs, the criteria of more than one shelf may apply to a given instance of an alarm.

For example, assume the criteria of shelf 'A' includes only the resource 'R' and the criteria of another shelf 'B' only includes the alarm-type-id 'X'. The question in this case would be which shelf should be referenced by the leaf 'shelf-name' for an alarm instance where resource = R and alarm-type-id = X? Or maybe 'shelf-name' should be a leaf-list? What are your thoughts on this?

And since the key to the list 'shelf' is 'name' and no unique statements are used, it would be possible to define multiple shelfs with exactly the same criteria. Again, if the criteria apply to an alarm, which shelf should be referenced by the leaf 'shelf-name'?

Would not the leaf also be better named just 'shelf'?

Best regards
Nick

v2.23.0 | Report a Bug | By Email