Re: [YANG] new pyang errors

Phil Shafer <phil@juniper.net> Wed, 23 January 2008 20:53 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 1JHmbK-0004tZ-Vl; Wed, 23 Jan 2008 15:53:38 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHmbK-0004tT-0B for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 15:53:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHmbJ-0004tL-Mk for yang@ietf.org; Wed, 23 Jan 2008 15:53:37 -0500
Received: from exprod7og108.obsmtp.com ([64.18.2.169]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHmbJ-0006ib-7A for yang@ietf.org; Wed, 23 Jan 2008 15:53:37 -0500
Received: from source ([66.129.224.36]) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP; Wed, 23 Jan 2008 12:52:44 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 23 Jan 2008 12:47:58 -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 m0NKlw910558; Wed, 23 Jan 2008 12:47:58 -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 m0NKlsgC024661; Wed, 23 Jan 2008 20:47:55 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801232047.m0NKlsgC024661@idle.juniper.net>
To: j.schoenwaelder@jacobs-university.de
Subject: Re: [YANG] new pyang errors
In-reply-to: <20080123204316.GB13869@elstar.local>
Date: Wed, 23 Jan 2008 15:47:54 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 23 Jan 2008 20:47:58.0652 (UTC) FILETIME=[3CB4CFC0:01C85E01]
X-Spam-Score: -4.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

Juergen Schoenwaelder writes:
>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.

So let's create an internet draft that defines a NETCONF capability
which adds an element to <get-config> called <with-defaults/> that
tells the NETCONF server to include default values in the <config>
reply, and to tag them with the "wd:default" attribute set to a
value of "true".  This should be a simple draft that we can get
thru the NETCONF WG in less than two years ;^)

Thanks,
 Phil


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