is a warning really an error?

["Kent Watsen" <kwatsen@juniper.net>]

All,

The spec specifies that an <rpc-error> can be returned to report a
warning, but warnings generally do not terminate processing while errors
do and <rpc-error> are returned whenever a "request cannot be completed
for any reason"

To highlight the conflict, consider:

1. Is it possible for <commit> to return a warning using <rpc-error>
without signaling that the transaction failed?

2. Is it possible for <edit-config> to return a warning using
<rpc-error> without signaling that the error-options (stop-on-error,
continue-on-error, rollback-on-error) were ignored?


Given this ambiguity, should "warning" should be removed from the spec?

Thanks,
Kent


--
Kent Watsen
Software Architect
Juniper Networks

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