Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-alarm-module-01 / features

From: NICK HANCOCK <[email-masked]>
Date: Mon, 26 Mar 2018 13:55:08 +0000

Hi Stefan,

In the module 'ietf-alarms@2018-02-01' included in draft-ietf-ccamp-alarm-module-01, the containers ‘alarm-inventory’ and ‘summary’ are not if-featured.
If-featuring these containers through separate features would make it easier for a step-wise implementation of the YANG Alarm Module, where at least an ‘alarm-list’ can be implemented early on with support for additional features being added over time. Or being able to provide rudimentary alarm management with just an ‘alarm-list’ where an inventory or summary would not be a necessity, such as small devices..
Also I feel that there is some inconsistency in the naming of the containers:

-          alarm-inventory

-          summary

-          alarm-list

For example, why ‘summary’ and not ‘alarm-summary’ or just ‘inventory’ instead of ‘alarm-inventory’.

Best regards
Nick
This message has been classified General Business by NICK HANCOCK on Monday, 26 March 2018 at 16:55:06.

From: CCAMP [mailto:[email-masked]] On Behalf Of stefan vallin
Sent: Thursday, February 08, 2018 1:42 PM
To: CCAMP ([email-masked]<mailto:[email-masked]>)
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-alarm-module-01.txt

Hi All!
We have now posted a new version of the draft. Updates based on comments from Balazs, Joey and Nick.

The major changes are:
1) Changed typedef operator-state into
- writeable-operator-state (not including includes shelved and un-shelved)
   can be set by an operator
- operator-state that can be read (includes shelved and un-shelved)

2) Added a leaf to the alarms in the shelf that states the name of the shelf.

3) Shelf criteria resource changed from leaf to leaf-list

4) Shelf criteria alarm type qualifier changed to regexp

5) Added text: "A server SHOULD describe how long it retains cleared/closed alarms: until manually purged or if it has an automatic removal policy.

6) Clarified that shelving/unshelving is done by shelf configuration and cannot be performed on individual alarms.

7) Clarified presedence order of resource naming ( 1 YANG instance identifier, 2 SNMP OID, 3 string )

8) Clarified that the alarm summary numbers do not include shelved alarms

9) Added a typedef resource-match which is a flexible way to identify resources.
Used in shelf criteria and alarm inventory

10) Clarified that an empty shelf indicates "shelf all”.

11) Added security considerations

12) Added reviewers to ack

There are still some outstanding items on the mailing list (from Nick and Joey).
But we felt it was time to publish the changes from some earlier discussions, see below.
Please let us know if we forgot something. I will top-post including these issues, summarising the discussions.
- severity filtering/shelving, needs further discussion
- temporal ordering, needs further discussion
- tagging of alarm types in alarm inventory, needs further discussion
- notifications for changed shelves, will add this in a later version
- probable cause description field, will add this in a later version

/stefan & martin

Stefan Vallin
[email-masked]<mailto:[email-masked]>
+46705233262

On 08 Feb 2018, at 12:33, [email-masked]<mailto:[email-masked]> wrote:

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-01.txt
            Pages           : 62
            Date            : 2018-02-08

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 RPCs 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-01<https://tools.ietf.org/html/draft-ietf-ccamp-alarm-module-01>
https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-alarm-module-01<https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-alarm-module-01>

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

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
[email-masked]<mailto:[email-masked]>
https://www.ietf.org/mailman/listinfo/ccamp<https://www.ietf.org/mailman/listinfo/ccamp>