Subject: Re: [Netconf] 4741bis - error-type

From: Martin Bjorklund <[email-masked]>
Date: Sun, 03 May 2009 22:21:44 +0200 (CEST)

Andy Bierman <[email-masked]> wrote:
> Martin Bjorklund wrote:
> > Hi,
> > The error-type is defined as:
> > error-type: Defines the conceptual layer that the error occurred.
> > But the error-type values do not match the names of the conceptual
> > layers in the picture in 1.1.
> > error-type         layer
> >    ----------         -----
> >    transport          transport protocol
> >    rpc                rpc
> >    protocol           operations
> >    application        content
> > Proposal:  add this clarification.
> > This means that if the error-type is 'rpc', the error happened in the
> > "rpc" layer, i.e. in the <rpc> element in the XML.
> > The error list in Appendix A lists the error 'unknown-element', which
> > can have error-type 'rpc' according to its specification.   But what
> > kind of XML would generate such an error in an rpc-reply?  If the
> > <rpc> element was received, any subelements are on the
> > protocol/operations layer.  If some element except for <rpc> is
> > received, an <rpc-reply> cannot be generated.
> > The same question applies to the errors 'unknown-namespace',
> > 'operation-not-supported' and 'operation-failed', and maybe
> > 'access-denied'.
> > Comments?
> > 
> 
> Not sure what OLD and NEW text is being proposed.
> There are errors that can occur while processing
> the <rpc> element, such as resource-denied.

In general, I think we should go through the error list and make sure
that each error-type is correct wrt the error.  In particular, I think
'rpc' should be removed from the errors listed above.

/martin