Re: [netconf] Adoption-suitability for draft-tao-netconf-data-export-capabilities

"" <> Mon, 10 August 2020 07:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C25ED3A0895 for <>; Mon, 10 Aug 2020 00:30:59 -0700 (PDT)
X-Quarantine-ID: <NnR7ZjHc8ksI>
X-Virus-Scanned: amavisd-new at
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 0.395
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NnR7ZjHc8ksI for <>; Mon, 10 Aug 2020 00:30:56 -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 E7E663A1410 for <>; Mon, 10 Aug 2020 00:30:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s201512; t=1597044642; bh=f1hQnU841ppPcRiZTKp0SJCPdfjgQ7k50DDgk5sPfAE=; h=Date:From:To:Cc:Subject:References; b=EfZ03pRiaBsOi0aonmsmPxbmwVmehOaCyF+AbCU00K0qro2Pz2c7mOf1LJOkRB89X sCV2yx68f2IUZjv/x3iDdJtSP3lSa2r4P/yP4E3hVNBGfH5WRgd792c3MdYYOexwIm +pI2HCDBU+GozAGPlX1AGHvv3udCRMv0GKM7gaH4=
Received: from cmcc-PC ([]) by (NewEsmtp) with SMTP id 7A88C8CE; Mon, 10 Aug 2020 15:30:40 +0800
X-QQ-mid: xmsmtpt1597044640tkp4g3vkz
Message-ID: <>
X-QQ-XMAILINFO: McXBXMazpRh64NiMYY+Z3JDiG8MFccpcWZEasbPt6QFbMfFUIpE/i/jFQFp3pn +Hie3Sblf66KSVLdmPXA6ydUmh3CeH2h14rfoV99l3a02v83M4jVg78jMdhLkFZTLTtVj8wC9nPm KhQc6YZr4DdpW/chlUV66igmqhIT3L550vPv1rkJK/p8NaP2OCeSsaah3HNSi+XcH3H5jflY7zCq JT+vAeC9W0K1y8S2+1wpbgAUdD0J9I0yQ+tSZ8SufjjGquoxeNcbqxMUD4dpI7p0k1riuoKCY1dz 3wyhGfceHFEl3IaBsUiiNTiW231Z62bLy+REZjSKSiVB75HJkPvN99A7DT29Xdh7zAvERv3FBob+ cu6o6QjB7BBQtK6aA7LNVleaM5Mv01YDkKrW5fShzWcGFcU3VBs7ycWEYLpEriHzLhAstXjLIY5B IH/UuFnGGezYTFi15eOFalT0KN69TcwXgnHq2+wwceRPAYUIVbsyu4aBwgayEx8LAsJqWg97QkyT k5fRxzoCpRWDgMtCyU7l3Uer6u68/2yGSRrmlmYnbvQXa4EkppUADF40kD9exmh20ewDFLKD6Zz9 iN/2bxotNgipV2d8OocZ7myPQu0JIZ37CtHOTFbJEVYN1fq7urIB8YQKBiTOWNF6NlQK2+YbrW5w tFGmZW7j6nqUpGbrneRMYbcNyrpNbc9QCXuxy9nC4r+JuQM3g2FNCPExjWfmngbsPwsm/Y3PqQCx uDDfRGXBKSqM6wkUuGEhhQa/llArMZDVNj
Date: Mon, 10 Aug 2020 15:32:54 +0800
From: "" <>
To: "Kent Watsen" <>
Cc: "" <>, duzongpeng <>
References: <>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail[cn]
Mime-Version: 1.0
Message-ID: <>
Content-Type: multipart/alternative; boundary="----=_001_NextPart834378467830_=----"
Archived-At: <>
Subject: Re: [netconf] Adoption-suitability for draft-tao-netconf-data-export-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: Mon, 10 Aug 2020 07:31:00 -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 enable subscriber and publisher to agree upon transport protocol (e.g., TCP, UDP), encoding format (e.g.,binary encoding,xml, json), encryption, compression mode to be used
and allow the client to select specific transport protocol, encoding format,etc when subscribing datastore node update.
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.
Addition data export 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.
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 &
From: Kent Watsen
Date: 2020-08-06 06:17
Subject: [netconf] Adoption-suitability for draft-tao-netconf-data-export-capabilities


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

   Title: Telemetry Data Export capability

      This document proposes a YANG module for telemetry data export
      capability which augments system Capabilities model and provides
      additional telemetry data export attributes associated with system
      capability for transport dependent capability negotiation.

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.