Re: [CCAMP] Comments regarding draft-ietf-ccamp-alarm-module-00

Hi!
Thanks for your response.
Is this something that should reside in the server?
I could argue this mapping should be done in the client, management system

br Stefan

Stefan Vallin
stefan@wallan.se
+46705233262

> On 12 Jan 2018, at 16:19, NICK HANCOCK <nick.hancock@adtran.com> wrote:
> 
> Hi Stefan,
>  
> Your comment:
>  
> Makes sense, I think we should add this capability to the alarm inventory. So the system publishes its possible alarm types (read-only).
> But each of those alarm types can have a configurable description leaf.
> Ok?
>  
> We believe that just a single configurable description leaf would be somewhat restrictive. We would rather take a more generic and extensible direction, whereby a client can map zero or more tagged values as required by his network implementation to an alarm-type-id and/or alarm-type-qualifier-match. For example, something like that shown below.
>  
> As configuration:
>  
>   +--rw custom-tags {custom-tags}?
>      +--rw custom-tag* [alarm-type-id alarm-type-qualifier-match tag-name]
>         +--rw alarm-type-id               alarm-type-id
>         +--rw alarm-type-qualifier-match  string
>         +--rw tag-name                    string
>         +--rw tag-value?                  tag-value
>  
> In the alarm inventory (state):
>  
>   +--ro alarm-type* [alarm-type-id alarm-type-qualifier]
>      +--ro alarm-type-id                       alarm-type-id
>      +--ro alarm-type-qualifier                alarm-type-qualifier
>      +--ro resource*                           string
>     :
>      +--ro custom-tags {custom-tags}?
>         +--ro custom-tag* [tag-name]
>            +--ro tag-name   string
>            +--ro tag-value? tag-value
>  
>  
> Best regards
> Nick
> This message has been classified Public by NICK HANCOCK on 12 January 2018 at 16:19:49.
>  
>  <>From: stefan vallin [mailto:stefan@wallan.se] 
> Sent: Thursday, January 11, 2018 2:29 PM
> To: NICK HANCOCK
> Cc: ccamp@ietf.org; JOEY BOYD
> Subject: Re: Comments regarding draft-ietf-ccamp-alarm-module-00
>  
> and your last comment…
>  
>  
>  
> 3. Mapping custom information to alarm types
>  
> Some operators require to be able to associate their own specific information with alarm types for use within their networks. Such a requirement could be supported within the alarm module through a generic mechanism whereby one or more tag/values could be mapped to an alarm-type-id and/or alarm-type-qualifier-match in a similar way as the list ‘x733-mapping’ allows a client to override the default X.733 mapping. Any mapped value would also need to be listed within the alarm inventory entry for that alarm-type and included within the ‘alarm-notification’.
>  
>  
> We believe that it would be advantageous if these additional requirements on alarm management were supported directly within the core alarm module to avoid the situation of each vendor implementing its own solution, which may then lead to interoperability issues between different vendors equipment.
>  
>  
> Makes sense, I think we should add this capability to the alarm inventory. So the system publishes its possible alarm types (read-only).
> But each of those alarm types can have a configurable description leaf.
> Ok?
>  
>  
> 
> 
>  
> Best regards
> Nick
> This message has been classified General Business by NICK HANCOCK on 09 January 2018 at 15:52:39.
>  
> From: CCAMP [mailto:ccamp-bounces@ietf.org <mailto:ccamp-bounces@ietf.org>] On Behalf Of internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
> Sent: Thursday, December 14, 2017 11:34 AM
> To: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>
> Cc: ccamp@ietf.org <mailto:ccamp@ietf.org>
> Subject: [CCAMP] I-D Action: draft-ietf-ccamp-alarm-module-00.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-00.txt
> Pages : 58
> Date : 2017-12-14
> 
> 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-00 <https://tools.ietf.org/html/draft-ietf-ccamp-alarm-module-00>
> https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-alarm-module-00 <https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-alarm-module-00>
> 
> 
> 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 <http://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 <mailto:CCAMP@ietf.org>
> https://www.ietf.org/mailman/listinfo/ccamp <https://www.ietf.org/mailman/listinfo/ccamp>