Re: Difference between get and get-config

[Martin Bjorklund <mbj@tail-f.com>]

"McDonald, Ira" <imcdonald@sharplabs.com> wrote:
> Hi,
> 
> I find it disturbing (but not surprising) that Andy
> and Martin suggested two different errors (and two
> different underlying reasons).  
> 
> The underspecified behavior of Netconf for various 
> error conditions will probably be a source of very
> widely divergent behavior on the part of Netconf
> clients - who apparently should expect just about
> anything in responses and somehow always gracefully 
> cope with it.

I agree with this.  In my generic NETCONF test suites I have comments
like this:

            # no std error message exists; accept any error


In this particular case, internally I use an error-code
'not-writable', which is then translated into the 'unknown-element',
with an <error-app-tag> of "not-writable".

'access-denied' is described as:
           Access to the requested RPC, protocol operation,
           or data model is denied because authorization failed.

  IMO, authorization didn't fail in this case.

'unknown-element' is described as:
           An unexpected element is present.

  The read-only element is unexpected (but not unknown...)


/martin

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