IETF Logo Mail Archive

Re: [YANG] new pyang errors

Ladislav Lhotka <lhotka@cesnet.cz> Wed, 23 January 2008 12:58 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 1JHfBM-0004Op-9d; Wed, 23 Jan 2008 07:58:20 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHfBL-0004OZ-7J for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 07:58:19 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHfBK-0004OR-Sz for yang@ietf.org; Wed, 23 Jan 2008 07:58:18 -0500
Received: from office2.cesnet.cz ([195.113.144.244]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHfBK-00064r-Hj for yang@ietf.org; Wed, 23 Jan 2008 07:58:18 -0500
Received: from [172.29.2.201] (asus-gx.lhotka.cesnet.cz [195.113.161.161]) by office2.cesnet.cz (Postfix) with ESMTP id 056F4D800CA for <yang@ietf.org>; Wed, 23 Jan 2008 13:58:18 +0100 (CET)
Subject: Re: [YANG] new pyang errors
From: Ladislav Lhotka <lhotka@cesnet.cz>
To: yang@ietf.org
In-Reply-To: <200801230532.m0N5W7Tt019859@idle.juniper.net>
References: <200801230532.m0N5W7Tt019859@idle.juniper.net>
Content-Type: text/plain; charset=utf-8
Organization: CESNET
Date: Wed, 23 Jan 2008 13:58:18 +0100
Message-Id: <1201093098.17304.156.camel@missotis>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

Phil Shafer píše v St 23. 01. 2008 v 00:32 -0500:

> This leads directly to my interpretation of "mandatory".  A mandatory
> config statement is one that some user or application must expressly
> configure.  If the configuration is valid without the statement,
> then it's not mandatory.

My definition of mandatory: mandatory configuration parameters are those
that are essential for device or protocol operation. It doesn't matter
whether they are set by the user/application, supplied from non-volatile
memory or perhaps even hardwired. A (full) configuration is valid only
if it contains all values that are declared as mandatory in the DM. 

Lada

-- 
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C



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

v2.8.7 | Report a Bug | By Email