Question on netconf-config-change behavior

NETCONF
1

Hi,

When I change a leaf value as default from some other value by ‘no’ command, the netconf-config-change notification is different from what I expected.
I think he actual operation is replace of a leaf value, but there is no target information on the notification.

I tested with an example of examples.confd/intro/1-2-3-start-query-model like this:

g5cu02# config t                  
Entering configuration mode terminal
g5cu02(config)# dhcp SubNets subNet 1.1.1.1 1.1.1.1 maxLeaseTime 1s         
g5cu02(config-subNet-1.1.1.1/1.1.1.1)# commit 
Commit complete.
g5cu02(config-subNet-1.1.1.1/1.1.1.1)# no maxLeaseTime 
g5cu02(config-subNet-1.1.1.1/1.1.1.1)# commit 
Commit complete.

.
The result was as follows:

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
    <ok/>
</rpc-reply>
<?xml version="1.0" encoding="UTF-8"?>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
    <eventTime>2017-06-16T16:30:59.137045+09:00</eventTime>
    <netconf-config-change xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-notifications">
        <changed-by>
            <username>admin</username>
            <session-id>0</session-id>
            <source-host>10.251.93.83</source-host>
        </changed-by>
        <datastore>running</datastore>
        <edit>
            <target xmlns:dhcpd="http://tail-f.com/ns/example/dhcpd">/dhcpd:dhcp/dhcpd:SubNets/dhcpd:subNet[dhcpd:net='1.1.1.1'][dhcpd:mask='1.1.1.1']</target>
            <operation>create</operation>
        </edit>
    </netconf-config-change>
</notification>
<?xml version="1.0" encoding="UTF-8"?>
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
    <eventTime>2017-06-16T16:31:04.145375+09:00</eventTime>
    <netconf-config-change xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-notifications">
        <changed-by>
            <username>admin</username>
            <session-id>0</session-id>
            <source-host>10.251.93.83</source-host>
        </changed-by>
        <datastore>running</datastore>
    </netconf-config-change>
</notification>
2

Hi,
Seems like that’s not the behaviour one would expect. If you have access to Tail-f support I suggest you file a ticket.
A workaround could be to create an app that listens to subscription events, do a cdb_diff_iterate() or a cdb_get_modifications() and send the desired NETCONF notification (from another thread) over the NETCONF stream.