[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: filtering problem
Andy Bierman <ietf@andybierman.com> wrote:
> Hi,
>
> There is another problem with filtering and the examples in sec 5: (!!!)
>
> The draft must say exactly where in the <notification> element
> that the <filter> is applied. The current text does not say anything.
Agreed.
> All the examples in sec. 5 are broken because the 'notification type'
> layer is missing.
I think it is ok. Specify that the filter is applied to the
'notificationContent' element as root (which is the abstract element).
> The examples assume the filters can only be
> applied to a conceptual datastore, just like the <rpc> filter.
>
> However, the most commonly needed filter is going to be
> on the notification type itself!
>
> Example (w/o namespaces):
>
> <notification>
> <configChange>
> <configChangeTime>date-time string...</configChangeTime>
> <configChangedBy>fred@example.com</configChangedBy>
> <configTarget>/interfaces/interface[name='eth0']</configTarget>
> ...
> </configChange>
> </notification>
>
> For simplicity, assume the manager just wants
> this one notification type. The filter is going to be something like:
>
> <filter type="subtree">
> <configChange/>
> </filter>
Yes, and IMO this is consistent with the examples.
/martin
> A filter for configChange just on a specific configTarget might be:
>
> <filter type="subtree">
> <configChange>
> <configTarget>/interfaces/interface[name='eth0']</configTarget>
> </configChange>
> </filter>
>
> The way the draft is now does not reflect how notifications are
> actually structured.
>
>
> 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/>
>
--
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/>