Re: [netmod] Question draft-wwx-netmod-event-yang

Qin Wu <> Mon, 02 December 2019 02:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A8C1712011C; Sun, 1 Dec 2019 18:03:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RxnD3ei3iI5q; Sun, 1 Dec 2019 18:03:15 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 63EE3120052; Sun, 1 Dec 2019 18:03:15 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTP id 141EB760AE97E673FC53; Mon, 2 Dec 2019 02:03:13 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 2 Dec 2019 02:03:12 +0000
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 2 Dec 2019 02:03:12 +0000
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Mon, 2 Dec 2019 02:03:11 +0000
Received: from ([]) by ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0439.000; Mon, 2 Dec 2019 10:01:44 +0800
From: Qin Wu <>
To: Igor Bryskin <>, draft-wwx-netmod-event-yang <>, NETMOD Group <>, Lou Berger <>
Thread-Topic: [netmod] Question draft-wwx-netmod-event-yang
Thread-Index: AdWotA+uLPZ+cUYSRNqhcdFI+Hb/TQ==
Date: Mon, 02 Dec 2019 02:01:43 +0000
Message-ID: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAA94AAFDEdggeml511mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netmod] Question draft-wwx-netmod-event-yang
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: Mon, 02 Dec 2019 02:03:18 -0000

Good point for consideration, Igor.  Sorry for late follow up.
I can add several consideration points into objective section
And generalized other objectives in the objective section.

发件人: Igor Bryskin []
发送时间: 2019年11月19日 23:59
收件人: Qin Wu <>; draft-wwx-netmod-event-yang <>; NETMOD Group <>; Lou Berger <>
主题: Re: [netmod] Question draft-wwx-netmod-event-yang

Lou, Qin, All.
I am glad you asked this. I thought about the same thing quite a bit myself. I wish you asked this 2 years back ;)
There are several  things to consider.  To name some:
1. How the client configures the ECAs. Currently  we suggest using NETCONF/RESTCONF,, but any configuration protocol could be, of course used just as well.
2. How do we express ECA components,  such as Action? Today we suggest in the form of NETCONF RPCs (either native, such as edit-config for re-configurations, or YANG model defined, such as TE path computations). But other platforms/modeling languages, such as, most obviously,  gNMI/gRPC/protonufs could be used just as well.
3.How an ECA execution thread talks to the client? Today we suggest using PUSH/PUSH extensions, but this could be expanded to communication channels of other types.
4. Etc.
In short, I like the suggestion very much. My only concern is this: we were told that we are setting already bar too high. It would be better to limit the work's scope to relatively simple PUSH extension to enable some basic RMON, elementary smart filters, etc. Your suggestion pushes the work in quite different direction - generic network ECA style automation.
I'd be happy to work on that, but I suggest to keep the generic architecture in mind as the end game and focus on delivering NETCONF/YANG solution first. This done quickly and properly, the generic extensions would be relatively straightforward IMHO.
Get Outlook for Android<>

On Tue, Nov 19, 2019 at 5:23 AM -0500, "Lou Berger" <<>> wrote:


     if you want to  be agnostic of protocol, the document will need to

be updated from its current netconf specific form.



On 11/19/2019 2:45 AM, Qin Wu wrote:

> Talking with our coauthors, we believe should not limit usage of this

> model only to netconf. Other protocols could be applied. Let us know

> if any update is needed.


> ------------------------------------------------------------------------

> 吴钦 Qin

> Mobile:+86-13914734360 (Mobile Number)





> *发件人: *Lou Berger>

> *收件人:

> *draft-wwx-netmod-event-yang >;NETMOD

> Group>

> *主题: *[netmod] Question draft-wwx-netmod-event-yang

> *时间: *2019-11-19 16:23:41


> Hi,


>      Authors, is there a reason tat the body of the text is only focused

> on netconf?  Why would you limit this work to any specific protocol?


> Thanks,


> Lou


> _______________________________________________

> netmod mailing list




netmod mailing list<>