[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proposed Update to Netconf Charter
Juergen Schoenwaelder wrote:
On Tue, Jul 05, 2005 at 04:40:30PM -0700, Andy Bierman wrote:
While all this sounds reasonable, I am really surprised that you
propose XPATH expressions given the lengthy discussion in the past
that XPATH expressions are too expensive for filtering. Or is it
because you expect access control on the 2nd tier not to be
mandatory to implement and an optional feature like XPATH
filtering?
I am envisioning that a simple absolute path expression be the mandatory
requirement and full XPATH expressions would be optional. This restricted
XPATH is what we have within the 'rpc-error' structure, and the WG
already agreed on this simple string format which happens to be a
particular subset of XPATH.
I must have missed that. Makes it even more interesting since subsetting
XPATH for filtering was also rejected in favour of a home-grown filtering
mechanism.
Actually this is totally consistent with the rpc-error design.
The user should be able to specify a qualified name (QName)
like 'error-info/bad-element', or specify a node via simple XPATH, like
the 'error-path' element.
The error-path element is optional so even this trivial XPATH usage
can be avoided, if desired.
IMO this is not inconsistent with the WG's choice to use subtree filtering.
This is an extremely restricted subset of XPATH, much easier to
define than a subset to do some real filtering.
/js
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/>