Re: [Netconf] 4741bis - error-type

Andy Bierman <andy@netconfcentral.com> Thu, 30 April 2009 15:19 UTC

Return-Path: <andy@netconfcentral.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 DE73628C131 for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 08:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level:
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 SI7ux6atSeXV for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 08:19:34 -0700 (PDT)
Received: from smtp122.sbc.mail.sp1.yahoo.com (smtp122.sbc.mail.sp1.yahoo.com [69.147.64.95]) by core3.amsl.com (Postfix) with SMTP id 4D83528C119 for <netconf@ietf.org>; Thu, 30 Apr 2009 08:19:34 -0700 (PDT)
Received: (qmail 22645 invoked from network); 30 Apr 2009 15:20:57 -0000
Received: from unknown (HELO ?127.0.0.1?) (andy@67.126.141.196 with plain) by smtp122.sbc.mail.sp1.yahoo.com with SMTP; 30 Apr 2009 15:20:56 -0000
X-YMail-OSG: eNPDwLcVM1ksWZAh6q4qU97zuW2nqPym2bAbd406vWRJXk9tsH8eABjrRFncjR_cQysKo0JwgsHqvalBfMny38MAbd9_5RBrV1GSlafpCPgL9esFOrzNW9Jr3Et9aktiEDO_0Co0YUJGIEalCvRt0Yu_5WrToIfY48LW3u0.DQ7eoDmsXu19u3LZV1r5wVjdb7fmBhIi6deBPLk1RMf.4fq_i_SCObxzELze5YLdaKfp.bRee6R900QDn9sHcXNetnDdx7ELyzd_pfL5WkjnwWHlPlwTrEZBJIh4DT6EIhc03cC3bfbY
X-Yahoo-Newman-Property: ymail-3
Message-ID: <49F9C1CF.9050106@netconfcentral.com>
Date: Thu, 30 Apr 2009 08:20:47 -0700
From: Andy Bierman <andy@netconfcentral.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Martin Bjorklund <mbj@tail-f.com>
References: <20090430.155908.05601603.mbj@tail-f.com>
In-Reply-To: <20090430.155908.05601603.mbj@tail-f.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
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: Thu, 30 Apr 2009 15:19:35 -0000

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.


> 
> /martin

Andy