Re: [YANG] new pyang errors

Ladislav Lhotka <lhotka@cesnet.cz> Fri, 25 January 2008 10:20 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 1JILfN-0004LG-RX; Fri, 25 Jan 2008 05:20:09 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JILfN-0004L8-1G for yang-confirm+ok@megatron.ietf.org; Fri, 25 Jan 2008 05:20:09 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JILfM-0004L0-ND for yang@ietf.org; Fri, 25 Jan 2008 05:20:08 -0500
Received: from office2.cesnet.cz ([195.113.144.244]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JILfM-0000p0-AJ for yang@ietf.org; Fri, 25 Jan 2008 05:20:08 -0500
Received: from [172.29.2.201] (asus-gx.lhotka.cesnet.cz [195.113.161.161]) by office2.cesnet.cz (Postfix) with ESMTP id 4B1D8D800C5 for <yang@ietf.org>; Fri, 25 Jan 2008 11:20:07 +0100 (CET)
Subject: Re: [YANG] new pyang errors
From: Ladislav Lhotka <lhotka@cesnet.cz>
To: yang@ietf.org
In-Reply-To: <200801250614.m0P6EJwJ036835@idle.juniper.net>
References: <200801250614.m0P6EJwJ036835@idle.juniper.net>
Content-Type: text/plain; charset=utf-8
Organization: CESNET
Date: Fri, 25 Jan 2008 11:20:06 +0100
Message-Id: <1201256406.24635.82.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: b19722fc8d3865b147c75ae2495625f2
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 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
-- 
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C



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