Re: [netconf] some comments on netconf-adaptive-subscription

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 25 June 2021 16:09 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 EDCDF3A07B1; Fri, 25 Jun 2021 09:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 gNDgIjFbtCrt; Fri, 25 Jun 2021 09:09:35 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28FEA3A07B3; Fri, 25 Jun 2021 09:09:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id EE3ED38B97; Fri, 25 Jun 2021 12:11:21 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HHlk8pn4U8yF; Fri, 25 Jun 2021 12:11:19 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id BB00638B96; Fri, 25 Jun 2021 12:11:19 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id F2A08553; Fri, 25 Jun 2021 12:09:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Qin Wu <bill.wu@huawei.com>, netconf@ietf.org, "core\@ietf.org" <core@ietf.org>
In-Reply-To: <0ded93e29090419dabc5551e49dac97d@huawei.com>
References: <0ded93e29090419dabc5551e49dac97d@huawei.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Fri, 25 Jun 2021 12:09:31 -0400
Message-ID: <30012.1624637371@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/McQtzxrcXdQy8w7sgCiDTSsD_1w>
Subject: Re: [netconf] some comments on 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: Fri, 25 Jun 2021 16:09:40 -0000

Qin Wu <bill.wu@huawei.com> wrote:
    > [Qin]: That's a good suggestion, WiFi provides a good use case for this
    > adaptive subscription mechanism. we did try some existing published
    > YANG models, but it seems YANG models size is too big.  That's why we
    > create simplified Wifi mac example Module. If you can provide a link to
    > CHIP/MATTER WIFI statistics module, we are happy to quote that existing
    > module.

The CHIP/MATTER document not public yet, but Huawei is a member and can get the document.
But, it's not a YANG module.  The fact that they have a set of wifi
statistics in their base definition argues that there ought to be an
equivalent YANG model though.

    > [Qin]: The intention is to optimize the existing YANG push mechanism
    > for NETCONF/RESTCONF and other management protocols. And the network
    > device can support multiple capture periodic intervals, the mechanism
    > we introduce is to allow the network device switch to different capture
    > periodic interval automatically without asking the NMS for permission
    > each time. I hope this clarifies.

yes, I understood that from the document.

    > [Qin]: I am also hoping RESTCONF and CORECONF can work together, but
    > they seems to look into different use cases (constrained device
    > management vs unconstrained device management) .  I am not sure we
    > should generalized RESTCONF and CORECONF into a single protocol.

That's not what I'm suggesting.
I'm asking, if bandwidth is an issue, why not use a smaller encoding.
And, why not integrate with CoAP Observe?

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide