Re: [YANG] errors

Andy Bierman <ietf@andybierman.com> Thu, 24 January 2008 21:01 UTC

Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI9CZ-0001XA-Ga; Thu, 24 Jan 2008 16:01:35 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JI9CX-0001Ok-Ra for yang-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 16:01:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI9CX-0001Mb-HC for yang@ietf.org; Thu, 24 Jan 2008 16:01:33 -0500
Received: from smtp121.sbc.mail.sp1.yahoo.com ([69.147.64.94]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JI9CV-0000cP-5P for yang@ietf.org; Thu, 24 Jan 2008 16:01:33 -0500
Received: (qmail 93926 invoked from network); 24 Jan 2008 21:01:30 -0000
Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@68.120.83.75 with plain) by smtp121.sbc.mail.sp1.yahoo.com with SMTP; 24 Jan 2008 21:01:29 -0000
X-YMail-OSG: 4rmDmA4VM1kYN6eY3uium26UNPGt5GSQFZTQH8stdhBqc67n
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4798FCA9.60500@andybierman.com>
Date: Thu, 24 Jan 2008 13:01:29 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Martin Bjorklund <mbj@tail-f.com>
Subject: Re: [YANG] errors
References: <20080124194143.GC16515@elstar.local> <20080124.212822.254714100.mbj@tail-f.com> <4798F7CF.3010203@andybierman.com> <20080124.214232.175587160.mbj@tail-f.com>
In-Reply-To: <20080124.214232.175587160.mbj@tail-f.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: yang@ietf.org
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org

Martin Bjorklund wrote:
> Andy Bierman <ietf@andybierman.com> wrote:
>> Martin Bjorklund wrote:
>>> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
>>>> On Thu, Jan 24, 2008 at 08:41:49AM -0800, Andy Bierman wrote:
>>>>
>>>>> What if the DM writer wants to raise an existing standard error?
>>> That's what I meant when I wrote that the raise-error is in addition
>>> to the standard errors.  I.e. nothing needs to be done in the DM for
>>> this scenario.
>>>
>> except there has to be a CLR that no error-app-tag value can be
>> one of the standard error-tag values. 
> 
> Why?
> 
> 

error lock-denied {
   error-tag operation-failed;
}

  ...
  raise-error lock-denied;


Is this raise-error for the standard lock-denied or for the
vendor error called lock-denied, defined in the same module?


> /martin
> 
> 


Andy



_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang