[Netconf] 4741bis - error-path
Martin Bjorklund <mbj@tail-f.com> Thu, 30 April 2009 14:00 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 7A2283A6A2F for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 07:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, 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 ndDUYnwtuW+w for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 07:00: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 AF8433A68CC for <netconf@ietf.org>; Thu, 30 Apr 2009 07:00: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 3CDB0616010 for <netconf@ietf.org>; Thu, 30 Apr 2009 16:01:42 +0200 (CEST)
Date: Thu, 30 Apr 2009 16:01:41 +0200
Message-Id: <20090430.160141.138853286.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-path
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 14:00:20 -0000
Hi,
The <error-path> element is defined as
Contains the absolute XPath [2] expression identifying
the element path to the node that is associated with the error
being reported in a particular rpc-error element. This element
will not be present if no appropriate payload element can be
associated with a particular error condition, [...]
It is not clear what the root node is in this XPath expression, but
from the text above which talks about "payload", it seems the root
node must be /rpc.
But this means that an operation like this:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0
message-id="101">
<validate>
<source>
<candidate/>
</source>
</validate>
</rpc>
which may detect errors in the data store cannot use <error-path> to
refer to invalid elements in the candidate config.
Is the intention that such data store errors should be data model
specific and out of scope for this document?
/martin
- [Netconf] 4741bis - error-path Martin Bjorklund
- Re: [Netconf] 4741bis - error-path Andy Bierman
- Re: [Netconf] 4741bis - error-path WashamFan
- Re: [Netconf] 4741bis - error-path Martin Bjorklund