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

王巍 <> Tue, 18 August 2020 12:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 300003A098E for <>; Tue, 18 Aug 2020 05:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.198
X-Spam-Status: No, score=0.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, PDS_TONAME_EQ_TOLOCAL_HDRS_LCASE=1.997, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Y-FnRbR1bzMG for <>; Tue, 18 Aug 2020 05:35:06 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EA76A3A092E for <>; Tue, 18 Aug 2020 05:35:05 -0700 (PDT)
Received: from clientip- (unknown []) by (HERMES) with SMTP id 57C45280093; Tue, 18 Aug 2020 20:34:57 +0800 (CST)
Received: from ([]) by App0021 with ESMTP id 3c84be8d805141988dab4db217ed8685 for; Tue Aug 18 20:34:57 2020
X-Transaction-ID: 3c84be8d805141988dab4db217ed8685
X-filter-score: filter<0>
X-MEDUSA-Status: 0
Date: Tue, 18 Aug 2020 20:34:56 +0800 (CST)
From: =?UTF-8?B?546L5beN?= <>
To: kent+ietf <>, netconf <>
Message-ID: <1803942779.26483.1597754097736@localhost>
MIME-Version: 1.0
Content-type: multipart/mixed; boundary="----=_Part_26482_1031994797.1597754096515"
X-HERMES-SET: Ir/5xdyPhtw/nKWlnb3tlh2opR3wkHKvQ6wxUNjG5Bw=
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 12:35:09 -0000


Hi all,

1) is the problem important for the NETCONF WG to solve?
I believe that it is important to capture characteristics data or KPI data for service assurance application and reduce the amount of
unnecessary data to be streamed out to the destination. Telemetry data tagging capability draft provides telemetry data classification and
help the client only fetch characteristics data.
And I also believe that the NETCONF WG is the appropriate WG for this work.
draft-ietf-netconf-notification-capabilities defines server capabilities advertisement and provides a good basis for Telemetry data tagging capability draft.

2) is the draft a suitable basis for the work?
I have review v-02 and believe it provides a sound basis for this work. Also if I remember correct, the demo on this idea has been presented in one of hackathon in last year.
If this work gets adopted, I am willing to review it and contribute to the discussion.

Best Regards,



Wei Wang

China Telecom

发件人: netconf [] 代表 Kent Watsen
发送时间: 2020 86 6:18
主题: [netconf] Adoption-suitability for draft-tao-netconf-notif-node-tag-capabilities


Per the previous email sent moments ago, the chairs would like to solicit input on the following draft:

Title: Self-explanation data Node tag capability

Link:" rel="nofollow">

Before a client application subscribes to updates from a datastore,

server capabilities related to "Subscription to YANG Datastores" can

be advertised using YANG Instance Data format. These server

capabilities can be documented at implement time or reported at run-


This document proposes a YANG module for self-explanation data Node

tag capability which augments system capabilities model and provide

additional self-explanation data node attributes associated with node

selectors within per-node capabilities.

In particular, please discuss adoption-suitability as it regards to the following questions:

1) is the problem important for the NETCONF WG to solve?
2) is the draft a suitable basis for the work?

PS: this message is itself not an adoption poll, but rather an attempt to gauge interest/support for a potential future adoption poll.