Generic description in RFC 8639, sec. 2.5, the specific configuration is described in RFC 8641, sec 4.2.
The netopeer2-server implements the configured subscription by subscribing for the changes of /ietf-subscribed-notifications:subscriptions/subscription in sysrepo. The sysrepo subscription can be done a similar way as in /notifications:create-subscription callback (np2srv_rpc_subscribe_cb()). Processing the event streams can be then done the same way as the standard NETCONF Notifications.
The monitored subscriptions configuration should be filtered to cover only the on-change subscriptions. The periodic subscriptions are supposed to be handled differently according to #797.
Supported features from ietf-subscribed-notifications module:
- encode-json
- encode-xml
- replay
- subtree
- xpath
Generic description in RFC 8639, sec. 2.5, the specific configuration is described in RFC 8641, sec 4.2.
The netopeer2-server implements the configured subscription by subscribing for the changes of
/ietf-subscribed-notifications:subscriptions/subscriptionin sysrepo. The sysrepo subscription can be done a similar way as in/notifications:create-subscriptioncallback (np2srv_rpc_subscribe_cb()). Processing the event streams can be then done the same way as the standard NETCONF Notifications.The monitored subscriptions configuration should be filtered to cover only the
on-changesubscriptions. Theperiodicsubscriptions are supposed to be handled differently according to #797.Supported features from
ietf-subscribed-notificationsmodule: