IETF Logo Mail Archive

Re: [YANG] new pyang errors

Ladislav Lhotka <lhotka@cesnet.cz> Wed, 23 January 2008 07:25 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 1JHZyq-00053f-CF; Wed, 23 Jan 2008 02:25:04 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHZyp-00053X-PN for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 02:25:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHZyp-00053K-Af for yang@ietf.org; Wed, 23 Jan 2008 02:25:03 -0500
Received: from office2.cesnet.cz ([195.113.144.244]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHZyn-0005fN-CA for yang@ietf.org; Wed, 23 Jan 2008 02:25:02 -0500
Received: from [172.29.2.201] (asus-gx.lhotka.cesnet.cz [195.113.161.161]) by office2.cesnet.cz (Postfix) with ESMTP id 55D75D800C7 for <yang@ietf.org>; Wed, 23 Jan 2008 08:24:58 +0100 (CET)
Subject: Re: [YANG] new pyang errors
From: Ladislav Lhotka <lhotka@cesnet.cz>
To: yang@ietf.org
In-Reply-To: <200801230532.m0N5W7Tt019859@idle.juniper.net>
References: <200801230532.m0N5W7Tt019859@idle.juniper.net>
Content-Type: text/plain; charset=utf-8
Organization: CESNET
Date: Wed, 23 Jan 2008 08:24:57 +0100
Message-Id: <1201073097.17304.22.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: 7655788c23eb79e336f5f8ba8bce7906
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 St 23. 01. 2008 v 00:32 -0500:
> Ladislav Lhotka writes:
> >Relying on common universal
> >defaults would make the system fragile.
> 
> As will shipping voluminous defaults.
> 
> Visibility into defaults is a distinct issue from carrying the
> defaults in the configuration database.  If I have an object with
> 50 fields where only 2 or 3 are set on each instance, carting around
> fully-fleshed configs will be incredibly annoying.

It would be sufficient if managers get the full configuration at the
start of each session so that they can be sure what the actual data are.
Then edit-configs etc. can include just the necessary parts. And by full
configuration I mean exactly this, with no hidden assumptions.

Lada

-- 
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C



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

v2.8.7 | Report a Bug | By Email