Re: retrieval filtering decision points

[Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>]

On Thu, Jun 10, 2004 at 10:42:41AM -0700, Andy Bierman wrote:
 
> The WG is deeply divided over subtree filtering vs. partial Xpath
> for the solution to retrieval filtering for the <get-config> and
> <get> operations.  The XML Directorate seemed to be divided as
> well on the value of our Xpath subset or the potential harm of our
> subtree filtering.  I am going to try to separate out the various
> decision points, some of which appear to have WG consensus already.

[...]

Are you saying that the netconf protocol only supports an empty filter
(which does not filter at all) and full xpath filtering becomes a 
capability? I think this pretty much makes sense as a way out of this
deadlock situation.

Of course, it leaves it to the vendors and the market to decide where 
the boundary between small and not so small devices is. And by saying 
no filtering is the lowest bound common denominator, not so smart 
applications will always do a full dump and filter on the manager side 
to avoid dealing with different capabilities. (But something like that
will happen whenever we have different filtering capabilities.)

What I do not yet understand is how namespaces play with this. I guess
this needs more thought and investigation.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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