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

"duzongpeng@foxmail.com" <duzongpeng@foxmail.com> Mon, 10 August 2020 08:56 UTC

Return-Path: <duzongpeng@foxmail.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0452A3A1486 for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 01:56:47 -0700 (PDT)
X-Quarantine-ID: <RPB_jcgazNg7>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 0.395
X-Spam-Level:
X-Spam-Status: No, score=0.395 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=1.5, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 RPB_jcgazNg7 for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 01:56:44 -0700 (PDT)
Received: from qq.com (out203-205-251-26.mail.qq.com [203.205.251.26]) (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 0FE2C3A0EA4 for <netconf@ietf.org>; Mon, 10 Aug 2020 01:56:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1597049791; bh=X67G3sMIVZPOjKw/2QVV5z55xmGXNU+C4coUt52YV3Y=; h=Date:From:To:Cc:Subject; b=qe436vRJosmvxeDjGTFiX1LiO4SGCNIv6ZVEz0SnEAFReqnQxZthUYdgmf0U9xens 7Gb/AAklI/8eYxGlmUXF/9OdTJu/aShjL8SF5gKJnZYz1SFY0noi8XdpMU84XxmtCO 43jAljuZEw49dq3wLNhT3GqIRodWmqsn9yJmTOLc=
Received: from cmcc-PC ([221.130.253.135]) by newxmesmtplogicsvrszc8.qq.com (NewEsmtp) with SMTP id E1D0DC4D; Mon, 10 Aug 2020 16:56:29 +0800
X-QQ-mid: xmsmtpt1597049789thnrhwnzp
Message-ID: <tencent_CDF031B451A93D44C9943740ADFA5CB21B0A@qq.com>
X-QQ-XMAILINFO: MB+SFuOmSM04TjWW/7l+hIPcD78BOSLiXzBy6PfYgo+0hWHxiFRmkHAXomjh1n 5ad1StMu5wrf8ZVivX4AYXXAvlGFs8k5fFPi6xcMlUkqx8CgvkIkAmEWY3r1PQJIuckbTGZu3W67 dAQA7llJfNJu0fBZcutJDQE6pGPZdkyXiAzJCK76NrtCaDv/56VRXFTcd0Hud3RqKyOv14KDyaUk yJHOm4nD7Pr4h8tkVXEMxr4xNGShommIaOByNDH7nkt6exzDQzZ4OQaWRrW+U5viLXyMiqNtvpw3 CYfzqjfQhPDyv49GaYItT10XYXwpGKKnuMZS5CZgoniV261Tf2LlQzx5ODyMUXQKMT2CeEATk9BB DyV3wnijlhvdE7myTkz/XJu1cQB7VwTbypH4OQcXlszFtnzHculLYPSeEr8mj7EseUMQwhRaIQdh MQREIGestTjhv98NpWsJeJnZ3dAuAzcuYyXjOaP7oOuHPC2aWob6OAXqUzt5Hy+mUIkuYweernUa e915eO1T9GmabZwLEQwq/T7U2wwLe3tRwAM8GhpSD5tmSIfTEhREEWSflLmOWJvS4G2xbdXgpXT4 gmzaWzQF5tXP4ZKsaNeHfl+UMel2Z7G51hflTXd83tMjBe173aF52cZ6GuBl4hU/a8R0WMwDf9Co 7163Xg0LlXcTQXvAl/Y41JnLxxcw3edtP+XCFxFvwPya+FGHnDxgufV7t+ZCOxPzjCI8WiXscqFC 3cl15dLB5ohNcWBuiHcZb4O0glYW616fZfQ5gxXOmox01TN5XGr4O4ig==
Date: Mon, 10 Aug 2020 16:58:42 +0800
From: "duzongpeng@foxmail.com" <duzongpeng@foxmail.com>
To: "Kent Watsen" <kent+ietf@watsen.net>
Cc: "netconf@ietf.org" <netconf@ietf.org>, duzongpeng <duzongpeng@chinamobile.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.16.188[cn]
Mime-Version: 1.0
Message-ID: <2020081016584181017018@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart766183077165_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/skyTAw1HlvEzbsmLnuiZp11QebM>
Subject: Re: [netconf] Adoption-suitability for draft-tao-netconf-notif-node-tag-capabilities
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Aug 2020 08:56:54 -0000

Hi, Chairs

    I would like to contribute to the draft. 

    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 provides a good basis for server capabilities advertisement and has already stable for publication.
Telemetry data tagging capability can be built on top of it.

    2) is the draft a suitable basis for the work?

I have read the latest version of the draft and believe it has been in good shape and served as a reasonable good starting point.
I have been aware one implementation has been demonstrated last year in IETF hackathon.
If this work gets adopted, I am willing to review this work as contributor and contribute to any discussion needed and 
we are interested to implement and plan to deploy this technology.


Best Regards
Zongpeng Du



duzongpeng@foxmail.com & duzongpeng@chinamobile.com
 
From: Kent Watsen
Date: 2020-08-06 06:17
To: netconf@ietf.org
Subject: [netconf] Adoption-suitability for draft-tao-netconf-notif-node-tag-capabilities

NETCONF WG,

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: https://tools.ietf.org/html/draft-tao-netconf-notif-node-tag-capabilities
   Abstract:

      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-
      time.

      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.

NETCONF Chairs