Re: [YANG] new pyang errors

Balazs Lengyel <balazs.lengyel@ericsson.com> Fri, 25 January 2008 11:19 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 1JIMaj-0001lN-Tx; Fri, 25 Jan 2008 06:19:25 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JIMaj-0001kW-6i for yang-confirm+ok@megatron.ietf.org; Fri, 25 Jan 2008 06:19:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIMai-0001hx-Rb for yang@ietf.org; Fri, 25 Jan 2008 06:19:24 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JIMai-00039N-6R for yang@ietf.org; Fri, 25 Jan 2008 06:19:24 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 6397A21482; Fri, 25 Jan 2008 12:19:23 +0100 (CET)
X-AuditID: c1b4fb3e-afe1dbb0000007e1-a8-4799c5bbe905
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 56A8421325; Fri, 25 Jan 2008 12:19:23 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Jan 2008 12:19:23 +0100
Received: from [159.107.197.224] ([159.107.197.224]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Jan 2008 12:19:22 +0100
Message-ID: <4799C5BA.5020606@ericsson.com>
Date: Fri, 25 Jan 2008 12:19:22 +0100
From: Balazs Lengyel <balazs.lengyel@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Ladislav Lhotka <lhotka@cesnet.cz>
Subject: Re: [YANG] new pyang errors
References: <200801250614.m0P6EJwJ036835@idle.juniper.net> <1201256406.24635.82.camel@missotis>
In-Reply-To: <1201256406.24635.82.camel@missotis>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 25 Jan 2008 11:19:22.0719 (UTC) FILETIME=[22DA0EF0:01C85F44]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
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

Mandatory in YANG means mandatory to configure.
Today YANG considers all mandatory and optional elements mandatory to implement.

Later we will probably define a conformance mechanism, then YANG will be able to say:

module foo defines 100 leafs and these 85 are mandatory to implement and the rest is optional.

We consider this conformance mechanism to belong to step to in the DML. AFAIK it is not really 
used in SNMP either. (We could start using mustImplement or something similar as a term for 
mandatory to implement.)

Balazs

Ladislav Lhotka wrote:
> Phil Shafer píše v Pá 25. 01. 2008 v 01:14 -0500:
>> "Randy Presuhn" writes:
>>> In the SNMP/SMI worlds, the "optionality" Ladislav refers to is
>>> handled by conformance statements, rather than the model per se.
>> Ah so maybe the confusion is "mandatory to implement" versus
>> "mandatory to configure".  YANG's mandatory statement is the latter.
> 
> Oh yes, this is the Pudels Kern :-) I am sorry I wasn't able to express
> myself so concisely. However, I still think Sec. 7.6.4 in the YANG draft
> can be understood as "mandatory to implement": >>If "mandatory" is
> "true", the node must exist in a valid configuration if its parent node
> exists.<< I guess it's again due to the different meanings of validity.
> 
> Lada
> 
>> YANG has no conformance mechanism.  Whether it appears in YANG-2.0,
>> I can't predict, but I'm hoping we can make base models that devices
>> can implement, with augmentations for additional config.
>>
>> Thanks,
>>  Phil
>>
>>
>> _______________________________________________
>> YANG mailing list
>> YANG@ietf.org
>> https://www1.ietf.org/mailman/listinfo/yang

-- 
Balazs Lengyel                       Ericsson Hungary Ltd.
TSP System Manager
ECN: 831 7320                        Fax: +36 1 4377792
Tel: +36-1-437-7320     email: Balazs.Lengyel@ericsson.com


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