[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: subtree filter spec vs. implementation

Phil Shafer wrote:

Andy Bierman writes:

1) If <users> is empty:
2) If <users> is not empty, but entry for 'fred' does not exist:


Both of these cases return an empty <configuration> element.
Filtering on something that isn't there gets you nothing.

    <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/8.0I0/junos";>
      <data>
        <configuration>
        </configuration>


Why are you returning the <configuration> element in this reply?
From the netconf POV, it seems the <filter> element in the
request maps to the <data> element in the reply.  If a 'FALSE' filter
adds nothing to the output, it seems like the <data> element should be empty.


Andy

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>