Re: Netconf! Part Deux

[Wes Hardaker <wjhns1@hardakers.net>]

Phil> I've been away for a bit (and will be out next week also), so
Phil> I'm still catching up on the netconf mailing list, but I'm
Phil> amazed that we're still having the same discussions.  I don't
Phil> know that I can add anything that hasn't been said repeatedly in
Phil> the past, but here's my take.....

Phil, thanks for a very well written set of arguments.

One additional point:

Phil> (III) The Cost of Using XPath
...
Phil> Neither the 'target' nor the 'value' elements can be validated against
Phil> an XML schema.  The type for 'target' has to be xsd:string (not sure
Phil> what the namespace is meant to achieve), and the type for 'value' has
Phil> to be xsd:any, allowing any xml content.  My app can't self-check the
Phil> configuration that I'm going to send to the device.

It's entirely likely it'll make access control mechanisms harder to
implement as well [you can't simply check the entire incoming chunk
against an automated access control validation service...  You'll
likely have to ask the low level code for help].  But I haven't
studied it as intently.


-- 
"In the bathtub of history the truth is harder to hold than the soap,
 and much more difficult to find."  -- Terry Pratchett

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