[CCAMP] 答复: YANG Alarm Module in CCAMP?

Zhenghaomian <zhenghaomian@huawei.com> Wed, 10 May 2017 01:42 UTC

Return-Path: <zhenghaomian@huawei.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 4CCC812EBA9; Tue, 9 May 2017 18:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 4JK9BHkMvur4; Tue, 9 May 2017 18:42:05 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 657E912EBA6; Tue, 9 May 2017 18:42:02 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML712-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGH37726; Wed, 10 May 2017 01:42:00 +0000 (GMT)
Received: from DGGEML403-HUB.china.huawei.com (10.3.17.33) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 10 May 2017 02:41:58 +0100
Received: from DGGEML503-MBS.china.huawei.com ([169.254.10.185]) by DGGEML403-HUB.china.huawei.com ([fe80::74d9:c659:fbec:21fa%31]) with mapi id 14.03.0301.000; Wed, 10 May 2017 09:41:45 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: stefan vallin <stefan@wallan.se>, Fatai Zhang <zhangfatai@huawei.com>
CC: "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, Martin Bjorklund <mbj@tail-f.com>
Thread-Topic: [CCAMP] YANG Alarm Module in CCAMP?
Thread-Index: AQHSyK1TVAEB/kzCPkaHSxKcrqO7t6HsyDag
Date: Wed, 10 May 2017 01:41:45 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43A260B36@DGGEML503-MBS.china.huawei.com>
References: <20170508.100942.1723888645272889243.mbj@tail-f.com> <AM2PR07MB09946D8FC13130E568BDEB95F0EE0@AM2PR07MB0994.eurprd07.prod.outlook.com> <VI1PR07MB1005AD5334CFBE2C0009B420F0EF0@VI1PR07MB1005.eurprd07.prod.outlook.com> <F82A4B6D50F9464B8EBA55651F541CF8AB50E23E@DGGEML501-MBS.china.huawei.com> <55A58B0B-281F-40CD-81E9-0F074CA61E95@wallan.se>
In-Reply-To: <55A58B0B-281F-40CD-81E9-0F074CA61E95@wallan.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.57.78.114]
Content-Type: multipart/alternative; boundary="_000_E0C26CAA2504C84093A49B2CAC3261A43A260B36DGGEML503MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.59126FE8.005B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.10.185, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: a4b75fb2823601d90fbf9f26858359c7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/lo9leyGbV5P-2HFO_sAw9jknNnA>
Subject: [CCAMP] 答复: YANG Alarm Module in CCAMP?
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: Wed, 10 May 2017 01:42:08 -0000

Hi, Stefan,

Thank you for bring the draft and the document, please find some of my comments as follow:


1)      I agree this work is useful, i.e., to have a generic alarm model draft in NETMOD. We had a draft on related topic as https://tools.ietf.org/html/draft-sharma-netmod-fault-model-01, unfortunately I have not got a chance to  compare the gap between this draft and yours, did you notice this draft?  And any comments?

2)      I am confused with your 2nd comment in the following email. When you said  ‘We will have a problem if different technologies will define different alarm-modules.’, IMHO I have an opposite opinion, if different technologies are using same alarm-modules, that would be a trouble. I understand there is a lot of common stuff among different technical alarms, but it is an adventurous assumption to restrict any tech-specific work. Could you confirm on this?

3)      If there is any tech-specific alarm work (may not be much), especially for L0/L1/microwave, that would belong to CCAMP. It is also difficult to conclude now whether it will be defining additional identities or model augmentation.

My 2 cents,
Haomian
发件人: CCAMP [mailto:ccamp-bounces@ietf.org] 代表 stefan vallin
发送时间: 2017年5月9日 18:15
收件人: Fatai Zhang
抄送: netmod-chairs@ietf.org; ccamp@ietf.org; Martin Bjorklund
主题: Re: [CCAMP] YANG Alarm Module in CCAMP?

Hi All!
Thanks for reading the doc.
A couple of comments:
1) I personally agree it fits in NETMOD, but the discussion in NETMOD said we would get much more relevant input in CCAMP since there is more alarm expertise in this group. So this is circular :)
2) I do not really agree when you say "extend it with technological aspect”, “optical alarm Yang should be in the scope of CCAMP” requires a dedicated CCAMP YANG module. The tech specific alarms are “alarm types” according to the alarm-module. Those are defined as YANG identities. So the tech specific part is “only” defining the corresponding identity. No real model here, just the identities. We will have a problem if different technologies will define different alarm-modules.
3) To Petch point on "I am conscious of how much time I spent on Sharon's SMI versions, which I did not then see in the wild”.
Same here :) I took part of a couple of implementations as well.
And that is one of the main reasons why I think an Alarm YANG is critical. Why do we not see the IETF Alarm MIB in the wild?
* It came too late, all devices had proprietary ways of reporting alarms (if devices had a notion of alarms at all….). Lets do an Alarm YANG now to avoid that problem.
* Since it had to add on top of existing MIBs it became a complex alarm mapping MIB (Mapping existing notfs into an alarm model) rather than an alarm MIB. That made it very complex.

Here is a presentation


Stefan Vallin
stefan@wallan.se<mailto:stefan@wallan.se>
+46705233262

On 09 May 2017, at 11:51, Fatai Zhang <zhangfatai@huawei.com<mailto:zhangfatai@huawei.com>> wrote:

Hi Daniele and all,

Yes, I agree with you.

As I said to Lou in another thread, I think the generic alarm Yang could be defined in either Netmod or Teas, but the technology specific such as optical alarm Yang should be in the scope of CCAMP.



Thanks

Fatai


-----邮件原件-----
发件人: CCAMP [mailto:ccamp-bounces@ietf.org] 代表 Daniele Ceccarelli
发送时间: 2017年5月9日 17:34
收件人: Daniele Ceccarelli; Martin Bjorklund; ccamp@ietf.org<mailto:ccamp@ietf.org>
抄送: netmod-chairs@ietf.org<mailto:netmod-chairs@ietf.org>; stefan@wallan.se<mailto:stefan@wallan.se>
主题: Re: [CCAMP] YANG Alarm Module in CCAMP?

Hi authors, NETMOD chairs, CCAMP WG,

i went through the document and, despite believing it's a super well written and understandable document, I don't think it fits in CCAMP.
This is a more generic work with a scope broader than CCAMP. At a first thought I would say TEAS, but also TEAS is not the right place since it's not related to traffic engineering.
The day you plan to extend it with technological aspect, then CCAMP would be its natural home.

Fatai, do you agree with the analysis?

BR
Daniele



-----Original Message-----
From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of Daniele Ceccarelli
Sent: lunedì 8 maggio 2017 16:40
To: Martin Bjorklund <mbj@tail-f.com<mailto:mbj@tail-f.com>>; ccamp@ietf.org<mailto:ccamp@ietf.org>
Cc: stefan@wallan.se<mailto:stefan@wallan.se>
Subject: Re: [CCAMP] YANG Alarm Module in CCAMP?

Hi Martin, Stefan,

thanks a lot for sharing the draft. I'll read it and let you know my personal opinion ASAP.

Working group, could you please do the same and share your thoughts?

Thanks
Daniele

-----Original Message-----
From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of Martin Bjorklund
Sent: lunedì 8 maggio 2017 10:10
To: ccamp@ietf.org<mailto:ccamp@ietf.org>
Cc: stefan@wallan.se<mailto:stefan@wallan.se>
Subject: [CCAMP] YANG Alarm Module in CCAMP?

Hi,

We have been working an a generic YANG module for alarm management for a while (draft-vallin-netmod-alarm-module).  The model is based on experience from several alarm management system over the years.  It has been presented in NETMOD (reflected in the draft name), but the NETMOD chairs felt that maybe CCAMP would be a better home for this draft.

So our question is if CCAMP would be interested in working on this draft?

The latest version is available as:
https://www.ietf.org/internet-drafts/draft-vallin-netmod-alarm-module-02.txt

 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.


/martin & stefan

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

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

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