<validate> operation somewhat broken

[Andy Bierman <ietf@andybierman.com>]

Hi,

IMO, the <validate> command is not actually useful for 'inline'
configuration validation.

The reason the edit-config operation does not have a 'test-only' mode
is because the validate operation is supposed to provide that feature.
Except it doesn't actually work.

Problem 1) Assumed target.  Since the <source> parameter is a choice,
the manager cannot specify a target -- it is assumed to be either
the <running> or <candidate> config.  There is no way to specify
a user-named config (url) as the target if the <config> inline mode is used.

Problem 2) Assumed default operation.  There is no way to pass the
default-operation parameter that would be used in the <edit-config>
along with the <config> element.  The <validate> operation is supposed
to come up with the same answer as an <edit-config> would in this mode,
but without this critical parameter, that is impossible.


The text in 8.6.4.1 does not match the XSD.
It does not indicate that 'inline config' or 'url' modes
are allowed here.  The only example shows the 'config name' variant.
Why didn't anybody bring this up until now?  Does anybody support
this operation?


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