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

Hi,

I am trying to understand the problem statement in this draft.
It appears to propose a complex self-monitoring system so that YANG Push
subscriptions can change their parameters on the fly to adapt to
changing network conditions. E.g. lower the 'period' parameter when
conditions are right, to produce more push-update records than normal.

The problem is somewhat interesting.
The filtering mechanisms in YANG Push are really awful and there is a need
to improve both filter and trigger mechanisms.  I don't think this draft
offers
a reasonable solution, but I encourage further experimentation.
Prove it works in real products then maybe it will be ready for
standardization.

Andy

On Wed, Aug 5, 2020 at 3:18 PM Kent Watsen <kent+ietf@watsen.net> wrote:

> 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
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>