Re: [YANG] new pyang errors

Phil Shafer <phil@juniper.net> Sat, 19 January 2008 17:39 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 1JGHet-0005KG-JA; Sat, 19 Jan 2008 12:39:07 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JGHer-0005KA-VU for yang-confirm+ok@megatron.ietf.org; Sat, 19 Jan 2008 12:39:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JGHel-0005K0-6D for yang@ietf.org; Sat, 19 Jan 2008 12:38:59 -0500
Received: from exprod7og106.obsmtp.com ([64.18.2.165]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JGHek-0003IC-Pw for yang@ietf.org; Sat, 19 Jan 2008 12:38:59 -0500
Received: from source ([66.129.224.36]) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP; Sat, 19 Jan 2008 09:38:56 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 19 Jan 2008 09:38:55 -0800
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m0JHco930927; Sat, 19 Jan 2008 09:38:55 -0800 (PST) (envelope-from phil@idle.juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id m0JHcUYi016993; Sat, 19 Jan 2008 17:38:35 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801191738.m0JHcUYi016993@idle.juniper.net>
To: Andy Bierman <ietf@andybierman.com>
Subject: Re: [YANG] new pyang errors
In-reply-to: <47914C9D.2090909@andybierman.com>
Date: Sat, 19 Jan 2008 12:38:30 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 19 Jan 2008 17:38:55.0910 (UTC) FILETIME=[2A40BC60:01C85AC2]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

Andy Bierman writes:
>The current draft clearly says that 'mandatory true' refers to the
>configuration database, not to whether the manager must provide
>an explicit value.
>I agree with the interpretation in the current draft.

Well, you agree with your interpretation of the draft ;^)

The issue isn't whether a leaf with a default has to appear
in any particular PDU, but whether a leaf with a default
"exists" until some{one,thing} creates it.  If leafs (and
non-presence containers) are automagically created "in the
configuration database", then configurations become big
and verbose, which is the opposite of what I want.  So
I don't want leafs with defaults to be considered "created".

And when I read the draft with that prespective, it agrees
with me.  So the draft is underspecified.  What outcome do
we want and what do need to add to the draft to ensure there
is only one possible reading of our spec?

Thanks,
 Phil


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