Re: [YANG] new pyang errors

Phil Shafer <phil@juniper.net> Wed, 23 January 2008 21:18 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 1JHmz8-0002Qo-N9; Wed, 23 Jan 2008 16:18:14 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHmz7-0002Qj-4v for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 16:18:13 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHmz6-0002Qb-Qr for yang@ietf.org; Wed, 23 Jan 2008 16:18:12 -0500
Received: from exprod7og110.obsmtp.com ([64.18.2.173]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHmz6-0002Em-9b for yang@ietf.org; Wed, 23 Jan 2008 16:18:12 -0500
Received: from source ([66.129.224.36]) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP; Wed, 23 Jan 2008 13:11:46 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 13:16:30 -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 m0NLGT923137; Wed, 23 Jan 2008 13:16:29 -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 m0NLGQNp024913; Wed, 23 Jan 2008 21:16:26 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801232116.m0NLGQNp024913@idle.juniper.net>
To: Martin Bjorklund <mbj@tail-f.com>
Subject: Re: [YANG] new pyang errors
In-reply-to: <20080123.215643.45475544.mbj@tail-f.com>
Date: Wed, 23 Jan 2008 16:16:26 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 23 Jan 2008 21:16:30.0159 (UTC) FILETIME=[38D80DF0:01C85E05]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: yang@ietf.org, 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

Martin Bjorklund writes:
>Andy has already defined such a capability in one of his drafts (I
>forgot which one...).

http://www3.ietf.org/internet-drafts/draft-bierman-ncx-ext-00.txt

This defines a set of protocol extensions:

     2.1.  test-only Enumeration  . . . . . . . . . . . . . . . . . .  5
     2.2.  with-defaults Attribute  . . . . . . . . . . . . . . . . .  7
     2.3.  with-metadata Attribute  . . . . . . . . . . . . . . . . .  9
     2.4.  last-modified Attribute  . . . . . . . . . . . . . . . . . 11

IMHO these should be distinct capabilities, since this is the way
NETCONF allows for such extensions.

One odd line (on first read) is:

   The 'with-defaults' attribute is defined in the namespace specified
   as the 'targetNamespace' in Section 3.  However, an agent should
   accept it even if no namespace is used.

This seems to play fast and loose with XML namespaces, which isn't
a good idea.

Another issue is that the draft puts these as attributes on the
<rpc>, instead of putting them inside the proper operations:

   If the 'with-defaults' attribute is
   present in the <rpc> element, for any of the protocol operations
   which return the contents of a configuration database, the agent will
   use the 'with-defaults' value to control default suppression.

I'm also missing where the metadata returned with with-metadata is
defined.

Thanks,
 Phil


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