Re: [netconf] Adoption-suitability for draft-wang-netconf-adaptive-subscription

"duzongpeng@foxmail.com" <duzongpeng@foxmail.com> Mon, 10 August 2020 08:06 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 5EFAC3A0D7C for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 01:06:34 -0700 (PDT)
X-Quarantine-ID: <FJLXHT_1u-At>
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 FJLXHT_1u-At for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 01:06:32 -0700 (PDT)
Received: from qq.com (out203-205-251-88.mail.qq.com [203.205.251.88]) (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 A2D723A09E0 for <netconf@ietf.org>; Mon, 10 Aug 2020 01:06:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1597046779; bh=XJJgrUDHoW3D/IXECEeEsOn0CQTvNJvGjuHgb+LpchU=; h=Date:From:To:Cc:Subject:References; b=uzMSC0gFjnbqLJYmTqKIaTkyex2dz9zBwK4nmd0ASbU5ou9/upd9+HXlijFwg6Myz PupK6LOMWegNEQYp6DlXJSYFcEzrPZxbSrPyLYXTwMLkRmPazZDtd7cVrjPxbgTEmb PufHM+zmyGRr494wH4HfIgULVDu3DhqMUju9eYPk=
Received: from cmcc-PC ([221.130.253.135]) by newxmesmtplogicsvrsza6.qq.com (NewEsmtp) with SMTP id 1910CC93; Mon, 10 Aug 2020 16:06:17 +0800
X-QQ-mid: xmsmtpt1597046777tm8xqkw4w
Message-ID: <tencent_7247C597EB42A1F89CB02FF175B6B5A8490A@qq.com>
X-QQ-XMAILINFO: MCieeIuk/bPLWif32+Fxz+NDESoHB9L47PWGAHVghcdQhjkXjC1wWL2XqkRbge 876tZtzhDKm1cmFYXpSp1ZqyVHckrUCO812EQmUkVpT2L5vgBkwVhE2Aywa10RmhXz0SZGUYuj5i YBzcApSMwwDJAkMHZe4NuFVccUfTO38bd7F4uYARpvXDiRRMisWkCT5cZ/RVuH5ct4LABe99An0g Ewmg5S9HNs/2omcdQntw5wisuItH5ql69wzdsHdJ2WMDXmXjD8z9UWIx6iwo7g4csldPh6cTdO4F Z7R1O5wNrnijEt4AKcfy4j7JamInoZxJTu1fDuj2n+HC9dpPG94zC2UlbpMpjciym5h4tyaiiXEo ceFU1YuUNKZd+u1e6PSha8r8/GI0uvNLEErqOR1HbZmORp/h+xBMGWY97Vlq9FRUiP4XpDZ+LqNE nFL2RNoFHnOz5nDMLGOfd7GMGZwQonEKs0IlStIBY4PJafLm6bEEqexLY2lPoSDm7OtlvG6R8gah Ijzo4Fq7+yXmWYlSwtrnnUJtn7Y1WfIr/YfK5yIrOSWltPjnsIokFKGSKW/Mpxc2Q+x/RCSmf2Qc I8BSOhtwt/7IqqGdyWKb/6gJ3SIrPqVXWyIPio3RHRu895mEJ1vwpxVjwMd14+sRdqqL9oGx6DLt 3O6z6NF7MNlvaeybJPREx2UYcrf+JntRa9qZVGHL9hSwoyhlG3abU1BSUCfRvLFuHBmHt28V8WUf UJ3JccajQY+v/GNrwm6p7Y3/6IaIYyjOgFi33/bbW3v00=
Date: Mon, 10 Aug 2020 16:08:30 +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>
References: <01000173c0b44d61-4df9b67b-47f9-46f5-9c91-6e00f466a5c5-000000@us-east-1.amazonses.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.16.188[cn]
Mime-Version: 1.0
Message-ID: <2020081016082979688613@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart238440573422_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/bUSXNwTtj3Flhgdq7eNhdXtpF-M>
Subject: Re: [netconf] Adoption-suitability for draft-wang-netconf-adaptive-subscription
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:06:34 -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 adjust the volume of telemetry traffic sent from publisher to the receivers based on situation changes Adaptive subscription draft
enables various subscription policy based on threshold support, timer-event-support and support multiple update interval, can effectively eliminate data collection 
performance bottleneck on the device.
And I also believe that the NETCONF WG is the appropriate WG for this work. RFC8639 and RFC8640 provide a good basis for this work.

    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 ongoing. One white paper has been planned for publication to make the whole community benefit from it.
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:18
To: netconf@ietf.org
Subject: [netconf] Adoption-suitability for draft-wang-netconf-adaptive-subscription
NETCONF WG,

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

   Title: Adaptive Subscription to YANG Notification
   Link: https://tools.ietf.org/html/draft-wang-netconf-adaptive-subscription
   Abstract:

      This document defines a YANG data model and associated mechanism
      enabling subscriber's adaptive subscriptions to a publisher's event
      streams at various different period intervals with which to report
      updates.  Applying these elements allows both subscriber and
      publisher to automatically adjust the volume of telemetry traffic
      sent from publisher to the receivers.


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