Re: [YANG] new pyang errors

"Randy Presuhn" <randy_presuhn@mindspring.com> Fri, 25 January 2008 04:15 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 1JIFyb-0004ea-UI; Thu, 24 Jan 2008 23:15:37 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JIFya-0004Uw-EP for yang-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 23:15:36 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIFya-0004S5-2j for yang@ietf.org; Thu, 24 Jan 2008 23:15:36 -0500
Received: from elasmtp-scoter.atl.sa.earthlink.net ([209.86.89.67]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JIFyZ-0007cX-Pe for yang@ietf.org; Thu, 24 Jan 2008 23:15:35 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=kuQrKQY0xul4dw88AggyXBZ9Dgo7KO97gn/m171QuZj3YR0CNnyZjH44obPep8Vl; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.82.180] (helo=oemcomputer) by elasmtp-scoter.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1JIFyW-0002VP-KN for yang@ietf.org; Thu, 24 Jan 2008 23:15:33 -0500
Message-ID: <000601c85f09$2fbe3c80$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <yang@ietf.org>
References: <200801250311.m0P3Bhbo036061@idle.juniper.net>
Subject: Re: [YANG] new pyang errors
Date: Thu, 24 Jan 2008 20:17:21 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8885d2a9c731cc8911766dc236590f0226b6fbf755886c6ab36350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.82.180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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

Hi -

> From: "Phil Shafer" <phil@juniper.net>
> To: "Ladislav Lhotka" <lhotka@cesnet.cz>
> Cc: <yang@ietf.org>
> Sent: Thursday, January 24, 2008 7:11 PM
> Subject: Re: [YANG] new pyang errors 
...
> >Again, my model: if a parameter is optional then the client cannot be
> >surprised if it is not in the configuration obtained by get-config and
> >attempts to set it are ignored or return a warning.
> 
> This would be disasterous and would render the entire effort of
> data modeling moot.  The data model is supposed to move us out
> of the Wild West and into a more civilized world.  If the locals
> can ignore parts of the law, then there is no law.  If you can't
> even find out what parts of the law are being ignored, you're lost.
...

In the SNMP/SMI worlds, the "optionality" Ladislav refers to is
handled by conformance statements, rather than the model per se.
In the CMIP/GDMO world, attributes are only optional to the
extent that they are associated with conditional packages, which
normally reflect varying conformance requirements, and whose
presence will be listed in the packages attribute.

Randy



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