[Netconf] 4741bis - error-type

Martin Bjorklund <mbj@tail-f.com> Thu, 30 April 2009 13:57 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 090FB3A6CDD for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 06:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id obHE3ZZ43KI3 for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 06:57:46 -0700 (PDT)
Received: from mail.tail-f.com (de-0316.d.ipeer.se []) by core3.amsl.com (Postfix) with ESMTP id 5033B3A6A2F for <netconf@ietf.org>; Thu, 30 Apr 2009 06:57:46 -0700 (PDT)
Received: from localhost (c213-100-167-236.swipnet.se []) by mail.tail-f.com (Postfix) with ESMTPSA id CCC50616010 for <netconf@ietf.org>; Thu, 30 Apr 2009 15:59:08 +0200 (CEST)
Date: Thu, 30 Apr 2009 15:59:08 +0200
Message-Id: <20090430.155908.05601603.mbj@tail-f.com>
To: netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.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
Subject: [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 13:57:47 -0000


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