Re: [Netconf] 4741bis - error-type

Martin Bjorklund <mbj@tail-f.com> Sun, 03 May 2009 20:20 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E73F3A6AB7 for <netconf@core3.amsl.com>; Sun, 3 May 2009 13:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.946
X-Spam-Level:
X-Spam-Status: No, score=-0.946 tagged_above=-999 required=5 tests=[AWL=-0.759, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8F1u2v1cU9Ry for <netconf@core3.amsl.com>; Sun, 3 May 2009 13:20:19 -0700 (PDT)
Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id 93EAD3A7117 for <netconf@ietf.org>; Sun, 3 May 2009 13:20:19 -0700 (PDT)
Received: from localhost (c213-100-167-236.swipnet.se [213.100.167.236]) by mail.tail-f.com (Postfix) with ESMTPSA id 6E796616032; Sun, 3 May 2009 22:21:44 +0200 (CEST)
Date: Sun, 03 May 2009 22:21:44 +0200
Message-Id: <20090503.222144.15510138.mbj@tail-f.com>
To: andy@netconfcentral.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <49F9C1CF.9050106@netconfcentral.com>
References: <20090430.155908.05601603.mbj@tail-f.com> <49F9C1CF.9050106@netconfcentral.com>
X-Mailer: Mew version 6.0.51 on Emacs 22.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: netconf@ietf.org
Subject: Re: [Netconf] 4741bis - error-type
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netconf>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 May 2009 20:20:20 -0000

Andy Bierman <andy@netconfcentral.com> 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