Re: Pre-release 2 of Notification Update

[Martin Bjorklund <mbj@tail-f.com>]

Andy Bierman <ietf@andybierman.com> wrote:
> tom.petch wrote:
> > Sharon
> > 
> > I raised the question of whether a filter would be applied to the event as it
> > would appear on the wire, or as it might appear in the datastore (thinking of
> > XPath roots and namespaces).  Andy reported back, after a hallway BoF with
> > Martin
> > 
> > 'The filtering in Notifications is different for 2 reasons,
> > as Martin has described in hallway BoFs...
> >    1) the filter applies to the notification message, not the conceptual
> >       NETCONF configuration database..'
> > 
> > I would like to see that explicit.  I suggest adding to 3.2.5.2.1 para 1
> > "Conceptually, the filter is applied to the event notification as it would
> > appear on the wire and not to it as it might appear in the conceptual NETCONF
> > database."

I suggested earlier that we should say that that the filter is applied
with the 'notificationContent' element as root (which is the abstract
element).

I don't think it's a good idea to add text about the conceptual
NETCONF database here - it has nothing to do with the notifications.

> Is the <notification> element constrained to contain
> exactly one child element?  (I think so.)

Yes, it is in the XSD in draft -09.


/martin

--
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/>