IETF Logo Mail Archive

Re: [YANG] new pyang errors

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 23 January 2008 20:43 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 1JHmRW-0002w4-UR; Wed, 23 Jan 2008 15:43:30 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHmRV-0002vY-SI for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 15:43:29 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHmRV-0002tz-HA for yang@ietf.org; Wed, 23 Jan 2008 15:43:29 -0500
Received: from hermes.jacobs-university.de ([212.201.44.23]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHmRV-0000x4-58 for yang@ietf.org; Wed, 23 Jan 2008 15:43:29 -0500
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id E6B098A33A; Wed, 23 Jan 2008 21:43:27 +0100 (CET)
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 31177-03; Wed, 23 Jan 2008 21:43:23 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 9E2C58A343; Wed, 23 Jan 2008 21:43:18 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id CA964488139; Wed, 23 Jan 2008 21:43:16 +0100 (CET)
Date: Wed, 23 Jan 2008 21:43:16 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Phil Shafer <phil@juniper.net>
Subject: Re: [YANG] new pyang errors
Message-ID: <20080123204316.GB13869@elstar.local>
Mail-Followup-To: Phil Shafer <phil@juniper.net>, Andy Bierman <ietf@andybierman.com>, yang@ietf.org, Ladislav Lhotka <lhotka@cesnet.cz>
References: <4796DD12.1@andybierman.com> <200801232035.m0NKZamr024518@idle.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200801232035.m0NKZamr024518@idle.juniper.net>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: yang@ietf.org, Ladislav Lhotka <lhotka@cesnet.cz>
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
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

On Wed, Jan 23, 2008 at 03:35:35PM -0500, Phil Shafer wrote:
 
> >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.

Yes, an option for <get-config> would be the clean solution. 

It would be nice if the IETF process would allow us to do good
engineering and not get us in the way. I think this is not the first
time we run into something that really should be "updated" in the
NETCONF protocol itself.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


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

v2.8.7 | Report a Bug | By Email