Re: [Netconf] 4741bis - error-severity

Andy Bierman <andy@netconfcentral.com> Thu, 30 April 2009 15:24 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 91BDC3A6F79 for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 08:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.394
X-Spam-Level:
X-Spam-Status: No, score=-2.394 tagged_above=-999 required=5 tests=[AWL=0.205, BAYES_00=-2.599]
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 Q5K7HuUGaANm for <netconf@core3.amsl.com>; Thu, 30 Apr 2009 08:24:11 -0700 (PDT)
Received: from n12.bullet.mail.mud.yahoo.com (n12.bullet.mail.mud.yahoo.com [209.191.125.209]) by core3.amsl.com (Postfix) with SMTP id C9AF13A6F66 for <netconf@ietf.org>; Thu, 30 Apr 2009 08:24:11 -0700 (PDT)
Received: from [68.142.200.221] by n12.bullet.mail.mud.yahoo.com with NNFMP; 30 Apr 2009 15:25:34 -0000
Received: from [68.142.201.64] by t9.bullet.mud.yahoo.com with NNFMP; 30 Apr 2009 15:25:34 -0000
Received: from [127.0.0.1] by omp416.mail.mud.yahoo.com with NNFMP; 30 Apr 2009 15:25:34 -0000
X-Yahoo-Newman-Id: 877710.67257.bm@omp416.mail.mud.yahoo.com
Received: (qmail 92603 invoked from network); 30 Apr 2009 15:25:34 -0000
Received: from unknown (HELO ?127.0.0.1?) (andy@67.126.141.196 with plain) by smtp109.sbc.mail.sp1.yahoo.com with SMTP; 30 Apr 2009 15:25:33 -0000
X-Yahoo-Newman-Property: ymail-3
Message-ID: <49F9C2E4.5000709@netconfcentral.com>
Date: Thu, 30 Apr 2009 08:25:24 -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.160226.69975872.mbj@tail-f.com>
In-Reply-To: <20090430.160226.69975872.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-severity
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:24:12 -0000

Martin Bjorklund wrote:
> Hi,
> 
> <error-severity> is defined to be 'error' or 'warning'.  In the list
> of errors in Appendix A, 'warning' never occurs.
> 
> Also, according to the XSD, <ok> and <rpc-error> cannot be returned at
> the same time, so there is no way to return <ok> and a warning at the
> same time.
> 
> There are three alternatives:
> 
>    1.  remove warning
> 
>    2.  fix warning so that it works
> 
>    3.  keep warning but clarify that it doesn't work
> 
> 
> Comments?
> 

Does anybody actually implement any warnings?
If not, then (1) is good.

In order to choose (2), we would have to understand
what we mean by a 'warning', and write it down.
Maybe if we did that the first time, we would have
tossed this error-severity field.


> 
> /martin

Andy