IETF Logo Mail Archive

Re: [YANG] new pyang errors

Phil Shafer <phil@juniper.net> Wed, 23 January 2008 20:37 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 1JHmLo-00089v-2p; Wed, 23 Jan 2008 15:37:36 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHmLl-00089c-QA for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 15:37:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHmLl-00089Q-BF for yang@ietf.org; Wed, 23 Jan 2008 15:37:33 -0500
Received: from exprod7og108.obsmtp.com ([64.18.2.169]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHmLc-00061M-0U for yang@ietf.org; Wed, 23 Jan 2008 15:37:33 -0500
Received: from source ([66.129.224.36]) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP; Wed, 23 Jan 2008 12:36:22 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Jan 2008 12:35:44 -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 m0NKZh904878; Wed, 23 Jan 2008 12:35:43 -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 m0NKZamr024518; Wed, 23 Jan 2008 20:35:36 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801232035.m0NKZamr024518@idle.juniper.net>
To: Andy Bierman <ietf@andybierman.com>
Subject: Re: [YANG] new pyang errors
In-reply-to: <4796DD12.1@andybierman.com>
Date: Wed, 23 Jan 2008 15:35:35 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 23 Jan 2008 20:35:44.0078 (UTC) FILETIME=[86DDB6E0:01C85DFF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: yang@ietf.org, Ladislav Lhotka <lhotka@cesnet.cz>
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:
>huh -- it uses up an extra second of bandwidth so the system is fragile?

No, the human element is fragile.  Having a config file littered
with values that the user didn't ask for and doesn't need it a
great way to help them ignore the parts of the config that they
did ask for and do need.

>There are lots of scenarios that cause an operator or application
>to need to full configuration, not just the values that do not have
>the default value.

If you see a value in this, make it an option to <get-config>.
It should not be the default behaviour.

Thanks,
 Phil


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

v2.8.7 | Report a Bug | By Email