Re: [netmod] New Version Notification for draft-wwx-netmod-event-yang-03.txt

Qin Wu <bill.wu@huawei.com> Wed, 23 October 2019 14:31 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 435BD120822; Wed, 23 Oct 2019 07:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 fw82SUGW1TJ3; Wed, 23 Oct 2019 07:31:00 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 759A912081C; Wed, 23 Oct 2019 07:31:00 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 4AA578E8238642272B3D; Wed, 23 Oct 2019 15:30:58 +0100 (IST)
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 23 Oct 2019 15:30:57 +0100
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 23 Oct 2019 15:30:57 +0100
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Wed, 23 Oct 2019 15:30:57 +0100
Received: from DGGEML531-MBS.china.huawei.com ([169.254.5.200]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0439.000; Wed, 23 Oct 2019 22:30:43 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>, Lou Berger <lberger@labn.net>, wangzitao <wangzitao@huawei.com>
CC: NetMod WG Chairs <netmod-chairs@ietf.org>, "draft-bryskin-netconf-automation-yang@ietf.org" <draft-bryskin-netconf-automation-yang@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, "draft-wwx-netmod-event-yang@ietf.org" <draft-wwx-netmod-event-yang@ietf.org>, "draft-sambo-netmod-yang-fsm@ietf.org" <draft-sambo-netmod-yang-fsm@ietf.org>
Thread-Topic: [netmod] New Version Notification for draft-wwx-netmod-event-yang-03.txt
Thread-Index: AdWJrb9m9t+rKjeMSvm32JSZ4OaKHA==
Date: Wed, 23 Oct 2019 14:30:42 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAA93961DF@dggeml531-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.108.52]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/tMxD9ycFg5jrFUg753bmi5i8n0A>
Subject: Re: [netmod] New Version Notification for draft-wwx-netmod-event-yang-03.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2019 14:31:05 -0000

Thanks Rob, just to remind draft-sambo-opsawg-ccamp-supa-ext-yang-fsm has been replaced by draft-sambo-netmod-yang-fsm-05 back in October 2017 and has been discussed twice before in the past netmod meetings.
I am happy to work with authors of three drafts to see how to rationalize these common interests effort.

-Qin
-----邮件原件-----
发件人: Rob Wilton (rwilton) [mailto:rwilton@cisco.com] 
发送时间: 2019年10月23日 21:32
收件人: Qin Wu <bill.wu@huawei.com>;; Lou Berger <lberger@labn.net>;; wangzitao <wangzitao@huawei.com>;
抄送: NetMod WG Chairs <netmod-chairs@ietf.org>;; draft-bryskin-netconf-automation-yang@ietf.org; netmod@ietf.org; draft-wwx-netmod-event-yang@ietf.org; draft-sambo-netmod-yang-fsm@ietf.org
主题: RE: [netmod] New Version Notification for draft-wwx-netmod-event-yang-03.txt

Hi Qin, Lou,

There it also draft-sambo-opsawg-ccamp-supa-ext-yang-fsm which, unless I am mistaken, also seems to be targeting the same area.

It seems like there is definitely interest in this area.  It would be nice if there could be a single standard solution, but perhaps the use cases are different enough that this doesn't make sense?

Thanks,
Rob


> -----Original Message-----
> From: netmod <netmod-bounces@ietf.org>; On Behalf Of Qin Wu
> Sent: 23 October 2019 14:15
> To: Lou Berger <lberger@labn.net>;; wangzitao <wangzitao@huawei.com>;
> Cc: NetMod WG Chairs <netmod-chairs@ietf.org>;; draft-bryskin-netconf- 
> automation-yang@ietf.org; netmod@ietf.org; draft-wwx-netmod-event- 
> yang@ietf.org
> Subject: Re: [netmod] New Version Notification for 
> draft-wwx-netmod-event- yang-03.txt
> 
> Lou:
> I am not against to harmonize with 
> draft-bryskin-netconf-automation-yang
> and actually both have already shared a lot of commonality on 
> motivation and use cases but the model proposed in draft-wwx reduce 
> its complexity and propose a more simple model design.
> A quick question to chair:
> Do you think we should start from complex advanced generalized model 
> with many features which not sure can be supported, or from simple 
> generic model in which the mechanism has been generalized in previous 
> several revisions and clarify the relationship with many related 
> standardized work such as YANG Push, Event MIB.
> 
> If clarifying the relationship with Event MIB is a concern, we could 
> remove it since Event MIB is just one of work that motivates to bring 
> this work up, in addition, hardware management model defined in 
> RFC8348 also clarify relationship with ENTITY-MIB, do you think 
> hardware management is something specific to MIB?
> 
> If I am wrong, please correct me.
> Regards!
> -Qin
> -----邮件原件-----
> 发件人: Lou Berger [mailto:lberger@labn.net]
> 发送时间: 2019年10月22日 20:38
> 收件人: wangzitao <wangzitao@huawei.com>;
> 抄送: netmod@ietf.org; NetMod WG Chairs <netmod-chairs@ietf.org>;; draft- 
> wwx-netmod-event-yang@ietf.org; draft-bryskin-netconf-automation- 
> yang@ietf.org
> 主题: Re: [netmod] New Version Notification for draft-wwx-netmod-event- 
> yang-03.txt
> 
> Michael/Authors/WG,
> 
> Thank you for this work.  One of the questions in looking at this 
> draft is the relationship to this draft to other individual work that 
> has been discussed in the WG, 
> notablyhttps://tools.ietf.org/html/draft-bryskin-
> netconf-automation-yang  . In looking at both drafts, I read it as 
> that the latter provides general infrastructure for 
> event-condition-actions (ECAs).  I'm less sure about your draft, in 
> reading it it too seems aimed at a general infrastructure, but it also 
> seems tailored to a specific set of ECAs that are aligned with the EVEN-MIB.
> 
> What is your/the authors intent?
> 
> If the former, perhaps it would be good for both sets of authors to 
> (at least try to) work together to come up with with a merged 
> document?  If the latter, does it make sense to adjust your draft to 
> document your use case using the more general mechanisms of the other draft?
> 
> What do you think?
> 
> Please let me know if you think I'm misreading or missed something here.
> 
> Thanks,
> Lou
> 
> On 10/15/2019 2:17 AM, wangzitao wrote:
> > Dear Working Group,
> >
> > As you recall that we presented the "draft-wwx-netmod-event-yang-02" 
> > in
> the last NETMOD session and got a good number of supports when the 
> chair polled in the room.
> > Recently we have a minor update on the draft based on Montreal 
> > meeting
> discussion, adding an appendix section to introduce how to reuse the 
> "trigger-grouping", more details please review the document.
> > https://tools.ietf.org/html/draft-wwx-netmod-event-yang-03
> >
> > We believe this draft is stable enough and would like to ask for WG
> adoption.
> >
> > Comments and suggestion are welcome!
> >
> > Best Regards!
> > -Michael(on behalf of authors)
> >
> > -----邮件原件-----
> > 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > 发送时间: 2019年10月15日 14:14
> > 收件人: wangzitao <wangzitao@huawei.com>;; Chongfeng Xie 
> > <xiechf@ctbri.com.cn>;; Qin Wu <bill.wu@huawei.com>;; wangzitao 
> > <wangzitao@huawei.com>;; Qin Wu <bill.wu@huawei.com>;
> > 主题: New Version Notification for draft-wwx-netmod-event-yang-03.txt
> >
> >
> > A new version of I-D, draft-wwx-netmod-event-yang-03.txt
> > has been successfully submitted by Michael Wang and posted to the 
> > IETF
> repository.
> >
> > Name:		draft-wwx-netmod-event-yang
> > Revision:	03
> > Title:		A YANG Data model for Policy based Event Management
> > Document date:	2019-10-13
> > Group:		Individual Submission
> > Pages:		30
> > URL:            https://www.ietf.org/internet-drafts/draft-wwx-netmod-
> event-yang-03.txt
> > Status:         https://datatracker.ietf.org/doc/draft-wwx-netmod-event-
> yang/
> > Htmlized:       https://tools.ietf.org/html/draft-wwx-netmod-event-yang-
> 03
> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-wwx-netmod-
> event-yang
> > Diff:           https://www.ietf.org/rfcdiff?url2=draft-wwx-netmod-
> event-yang-03
> >
> > Abstract:
> >     [RFC8328] defines a policy-based management framework that allow
> >     definition of a data model to be used to represent high-level,
> >     possibly network-wide policies.  This document defines an YANG data
> >     model for the policy based event management [RFC7950].  The policy
> >     based Event YANG provides the ability for the network management
> >     function (within a controller, an orchestrator, or a network
> element)
> >     to control the configuration and monitor state change on the network
> >     element and take simple and instant action when a trigger condition
> >     on the system state is met.
> >
> >
> >
> >
> > 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.
> >
> > The IETF Secretariat
> >
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod