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

Lou Berger <> Tue, 22 October 2019 12:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6E2AF120013 for <>; Tue, 22 Oct 2019 05:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (768-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Q_6o6XiCVVtA for <>; Tue, 22 Oct 2019 05:38:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DEC321200D7 for <>; Tue, 22 Oct 2019 05:38:21 -0700 (PDT)
Received: from (unknown []) by (Postfix) with ESMTP id 46798215E61 for <>; Tue, 22 Oct 2019 06:38:18 -0600 (MDT)
Received: from ([]) by cmsmtp with ESMTP id MtQYizbfd94wVMtQYiHlCf; Tue, 22 Oct 2019 06:38:18 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: v=2.3 cv=Q5b8Hb+a c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10:nop_charset_1 a=xqWC_Br6kY4A:10:nop_ipv6 a=XobE76Q3jBoA:10:nop_rcvd_month_year a=Vy_oeq2dmq0A:10:endurance_base64_authed_username_1 a=48vgC7mUAAAA:8 a=i0EeH86SAAAA:8 a=2z3Vzv4VAAAA:8 a=yIYjWox4XA6gY56VSBcA:9 a=7ZTrHm_VIiY28_0M:21 a=ZUGh0eov-TLtSLvX:21 a=QEXdDO2ut3YA:10:nop_charset_2 a=w1C3t2QeGrPiZgrLijVG:22 a=tJVlPwtRPE92R_5dfMPn:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=EW+P+vayYl1ohXnXxJ9y1c+QABwLy7NOL347EdSjQxM=; b=axJlh1X7L/Fp065cWOoLLADYOM WSfeOSpjzA2szBJJpimxloaeRx0cP2fiuGGlwU5c5iFMCszVdyTgihof+n3ZSbinnxhP81mh1FzE+ N/rQbat+Zk2rDxrunX1M//HIG;
Received: from [] (port=50137 helo=[IPv6:::1]) by with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <>) id 1iMtQX-003XAl-Rx; Tue, 22 Oct 2019 06:38:17 -0600
To: wangzitao <>
Cc: "" <>, NetMod WG Chairs <>,,
References: <>
From: Lou Berger <>
Message-ID: <>
Date: Tue, 22 Oct 2019 08:38:12 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
X-BWhitelist: no
X-Source-L: Yes
X-Exim-ID: 1iMtQX-003XAl-Rx
X-Source-Sender: ([IPv6:::1]) []:50137
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <>
Subject: Re: [netmod] New Version Notification for draft-wwx-netmod-event-yang-03.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 22 Oct 2019 12:38:28 -0000


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, notably  . 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.


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.
> 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)
> -----邮件原件-----
> 发件人: []
> 发送时间: 2019年10月15日 14:14
> 收件人: wangzitao <>; Chongfeng Xie <>; Qin Wu <>; wangzitao <>; Qin Wu <>
> 主题: 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:  
> Status:
> Htmlized:
> Htmlized:
> Diff: 
> 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
> The IETF Secretariat
> _______________________________________________
> netmod mailing list