IETF Logo Mail Archive

Re: [YANG] errors

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Thu, 24 January 2008 19:39 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 1JI7uw-0004tt-3O; Thu, 24 Jan 2008 14:39:18 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JI7uu-0004to-FB for yang-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 14:39:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI7uu-0004tg-51 for yang@ietf.org; Thu, 24 Jan 2008 14:39:16 -0500
Received: from hermes.jacobs-university.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JI7us-0007M8-Bb for yang@ietf.org; Thu, 24 Jan 2008 14:39:16 -0500
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id 57B698A32D; Thu, 24 Jan 2008 20:39:13 +0100 (CET)
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 23984-01; Thu, 24 Jan 2008 20:39:08 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 92ADF8A31C; Thu, 24 Jan 2008 20:39:08 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 6B6B148A069; Thu, 24 Jan 2008 20:39:06 +0100 (CET)
Date: Thu, 24 Jan 2008 20:39:06 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Martin Bjorklund <mbj@tail-f.com>
Subject: Re: [YANG] errors
Message-ID: <20080124193906.GB16515@elstar.local>
Mail-Followup-To: Martin Bjorklund <mbj@tail-f.com>, ietf@andybierman.com, yang@ietf.org
References: <20080124.153853.210376606.mbj@tail-f.com> <4798BFCD.3000706@andybierman.com> <20080124.185012.212081588.mbj@tail-f.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080124.185012.212081588.mbj@tail-f.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: yang@ietf.org
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
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

On Thu, Jan 24, 2008 at 06:50:12PM +0100, Martin Bjorklund wrote:

> You are right.  [checking rfc4741...] Hmm.  An rpc-error MUST include
> error-tag.  The list of error-tags is defined in rfc4741.  For each
> such tag, the corresponding error-severity is defined.  All tags have
> error-severity 'error'.  Conclusion: error-severity 'warning' can
> never be generated. !!?!?!

I mentioned this before. I agree error-severity as it is is useless
and I think we consider to remove it from NETCONF when the specs are
revised. Did I mention that it would be nice to have a NETCONF
maintenance activity? Even if it is just a web page to keep track of
the issues until the IETF gets to it?

/js 

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


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

v2.8.7 | Report a Bug | By Email