Re: [Netconf] notification access control

[Phil Shafer <phil at juniper.net>]

Andy Bierman writes:
>3.2, para 4:
>    After generation of the <notification> element, access control is
>    applied by the server.  If a session does not have permission to
>    receive the <notification>, then it is discarded for that session,
>    and processing of the internal event is completed for that session.

>I will assume an implementation may silently prune
>parts of the payload from the notification, due to access
>control policy.  The notification MUST be dropped
>if the <eventType> element would be filtered out,
>in violation of the <notification> element schema.

Yes, let's add this as an issue list for a future -bis, since an
implementation should be able to prune inappropriate elements from
the notification.

Also we should repair the word "after" in the above text, since
there isn't any explicit to generate the <notification> element at
all if no one is permitted to receive the content.

Thanks,
 Phil