IETF Logo Mail Archive

Re: [netconf] Adoption-suitability for draft-wang-netconf-bulk-subscribed-notifications

"duzongpeng@foxmail.com" <duzongpeng@foxmail.com> Mon, 10 August 2020 08:08 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 72C7D3A09E0 for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 01:08:26 -0700 (PDT)
X-Quarantine-ID: <Jdd7CsHi-xW9>
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 Jdd7CsHi-xW9 for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 01:08:23 -0700 (PDT)
Received: from qq.com (out203-205-251-27.mail.qq.com [203.205.251.27]) (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 0D9133A0807 for <netconf@ietf.org>; Mon, 10 Aug 2020 01:08:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1597046896; bh=vq4N2Qd4p+tn4dzZOUpk/fO8lmpdKshemE7YW5y+xl4=; h=Date:From:To:Cc:Subject:References; b=bkncOzQTFlk20LXkBRZokTSvjgByHqEamgmioOzKfRbPh6zl7yMAd/SG2iINA2su7 n+mGw3djH+aCnefuyrMRrzUiqq1qT5/DdvQNkU1Sunek9WQVH7gSJAN1PyYGMpIZpB FCUIZh/6wFgvITrvSkq0Qc2lFO0FpdZAA8A8/2s4=
Received: from cmcc-PC ([221.130.253.135]) by newxmesmtplogicsvrsza5.qq.com (NewEsmtp) with SMTP id 20DB808A; Mon, 10 Aug 2020 16:08:13 +0800
X-QQ-mid: xmsmtpt1597046893tb1rajgo2
Message-ID: <tencent_D4B911148D0F26FB395F5F5B831A5C546006@qq.com>
X-QQ-XMAILINFO: NRRSkgP6RcOlY+Z5uAqPF1Jv+ohv/WUPT3PcIR/rTG+b36kjVTXqhzX8altxWB 9zJujKeZi7JU6EDnc93AfR+nKkZfiUi1sfh4uXtJ1fDFxrUi1PokQuIWkoACFHSE4DzDvme3RcGy JB4edxWBhWetk399LdrcLpAxwq83vj7L62d/L9xRUI5gShwC6b5yD6oTJ+B/q3I0AuIKplu6zetL k35G4DxCxnQ8l8RsAjrSzUaXuTNRqyMdanihQs9IS1Z0on96tv3LdA7A7nR7wYCBlQVFr31tLWzs N8ZLgELph9yvxV/qlDeaSvFotJH6f+i5+tqsSFeEFj0GRuaWVlMDSKqpO2rkub4scQnpmxugrvvl UxnU6OXVB8e2fVqudmCtcShYCoXXVCJxZVEzEO3Ji7fdzeiIuIIwFxfZg1l0unb9CM/IRWVmYYlr 1VJcruA1Tfy9J4UA8LdQsLWFiNLhT/Hk8aN88kJ740CP/V7gMbITW9RsXJmXj14diK5jAZVYzpse Q2wR0/33Q3PBNar2uCgAt4pSaqN1V4gVKA9M65xHlYE/eJ2Xsv7SgvMB1cekuFhnR+3kiPU0CA40 eYY34l25esjQ92i6qsgh6wQm+J446k1CoG9CCErMdEl5QL/gXHrVgehbG6I78UyxJNr7JFC8WGcD 2Qg7l+xq6EeG+YDh6rvH9Qb0a6M+adT6dhaidjD5ggzCesFIlJoSurY7gHLnAYAA6PMkknrZ0vN2 crb/OyUg5BwBhXaWmdX5jTOXPXgUQLoyKycvxqngsigBX8HGo5aRaMCA==
Date: Mon, 10 Aug 2020 16:10:27 +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: <01000173c0b45676-dc00a30e-1234-45d2-ba20-131c9467110d-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: <2020081016102633273315@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart337600482385_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Uo0eWz7gb6FOc1HHm-LxyWVjTiA>
Subject: Re: [netconf] Adoption-suitability for draft-wang-netconf-bulk-subscribed-notifications
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:08:26 -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 allow the publishers to understand which specific subscriptions can be bundled together and which not.
Bulk Subscription can work together [I-D.ietf-netconf-notification-messages] and allow the publishers to report multiple notification in a single bundling message.
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.
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.


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-bulk-subscribed-notifications

NETCONF WG,

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

   Title: Bulk Subscription to YANG Event Notification
   Link: https://tools.ietf.org/html/draft-wang-netconf-bulk-subscribed-notifications
   Abstract:

      This document defines a YANG data model and associated mechanism that
      allows subscriber applications to bulk subscribe to publishers' event
      streams based on bundle group information such as bundle size and
      bundle latency.  This allows the publishers to report multiple
      notifications in a single bundling message.


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

v2.23.0 | Report a Bug | By Email