Re: [netconf] Adoption-suitability for draft-tao-netconf-notif-node-tag-capabilities

"" <> Tue, 18 August 2020 16:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 62A0E3A0EA4 for <>; Tue, 18 Aug 2020 09:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1FuudwPptOrI for <>; Tue, 18 Aug 2020 09:24:00 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 29B453A0EAE for <>; Tue, 18 Aug 2020 09:23:52 -0700 (PDT)
Received: from clientip- (unknown []) by (HERMES) with SMTP id 5BB442800A1; Wed, 19 Aug 2020 00:23:43 +0800 (CST)
Received: from ([]) by App0025 with ESMTP id 9bdd04c15fdb420a9f4a4f3fe13d6f8e for; Wed Aug 19 00:23:45 2020
X-Transaction-ID: 9bdd04c15fdb420a9f4a4f3fe13d6f8e
X-filter-score: filter<0>
X-MEDUSA-Status: 0
Date: Wed, 19 Aug 2020 00:23:45 +0800
From: "" <>
To: "" <>
X-Priority: 3
X-GUID: C2627684-010A-4266-AAAD-C2CE6AB89B84
X-Has-Attach: no
X-Mailer: Foxmail[cn]
Mime-Version: 1.0
Message-ID: <>
Content-Type: multipart/alternative; boundary="----=_001_NextPart544808438733_=----"
Archived-At: <>
Subject: Re: [netconf] Adoption-suitability for draft-tao-netconf-notif-node-tag-capabilities
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 18 Aug 2020 16:24:03 -0000

Dear all, 

Regarding the two questions, the comments are as follows:

1. Is the problem important for the NETCONF WG to solve?
I believe that it is important to retrieve different KPI data from various different data source and correlate them together and provide comprehensive view of the network quality or network health from different angles. In addition, it is important to eliminate noise data to be exported to the management plane. Telemetry data tagging and classification is crucial to help capture characteristics data and reduce amount of streamed data to the destination. And I also believe that the NETCONF WG is the appropriate WG for this work. draft-ietf-netconf-notification-capabilities separate notification capability model into system capability model and ietf-notification-capabilities model which serve as a good basis for telemetry data node capabilities definitions.

2. Is the draft a suitable basis for the work?
I have been aware MDT Telemetry tagging Hackathon project in IETF 106 which was demonstrated in both IETF 106 Hakcathon meeting and Hackdemo Happy Hour. I think this draft is mature enough and provide a solid basis for starting point. If this work gets adopted, I will be glad to review any update of this draft and contribute to relate discussion.

I believe it should move forward.

Best regards,

Yuan ZHANG 张园 

China Telecom Research Institute 中国电信研究院
Tel: +86-18918588990