[NGO] YANG augment-stmt

Andy Bierman <ietf@andybierman.com> Mon, 10 December 2007 16:29 UTC

Return-path: <ngo-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J1lVE-0004MC-TG; Mon, 10 Dec 2007 11:29:08 -0500
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1J1lVD-0004M6-H1 for ngo-confirm+ok@megatron.ietf.org; Mon, 10 Dec 2007 11:29:07 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J1lVD-0004Lp-6i for ngo@ietf.org; Mon, 10 Dec 2007 11:29:07 -0500
Received: from smtp114.sbc.mail.mud.yahoo.com ([68.142.198.213]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1J1lVC-0008Lr-Q7 for ngo@ietf.org; Mon, 10 Dec 2007 11:29:07 -0500
Received: (qmail 89256 invoked from network); 10 Dec 2007 16:29:06 -0000
Received: from unknown (HELO ?192.168.0.10?) (andybierman@att.net@68.120.85.122 with plain) by smtp114.sbc.mail.mud.yahoo.com with SMTP; 10 Dec 2007 16:29:05 -0000
X-YMail-OSG: zDuPZt4VM1loLw9uA.bKvxS.lNaqCI8ODRcw0wZfZ1FDGP1l
Message-ID: <475D68D5.50400@andybierman.com>
Date: Mon, 10 Dec 2007 08:27:01 -0800
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: yang <yang@ietf.org>, NETCONF Goes On <ngo@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc:
Subject: [NGO] YANG augment-stmt
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Errors-To: ngo-bounces@ietf.org

Hi,

Looking at the ABNF for the all-powerful augment statement,
I notice it can appear inside a list or inside an another augment,
anywhere a data-def-stmt can go in fact.

Since this clause does not instantiate any data where it
located, but rather at the target specified by the augment-arg-str,
the containment for the augment seems pretty much irrelevant,
except that the augment could be nested within N different 'when'
statements, nested inside obsolete nodes, etc.

The key in a list with an augment-stmt has no affect on the target data,
does it?

What does it mean to have an augment inside a grouping, so that
it is copied everywhere a 'uses' for that grouping is specified?

What is the use-case for augment inside augment?
That means while you are defining extra data to attach to /acme:foo
you also define some extra data for /a:bar/b:baz?

I have only seen augment examples that appear at the top-level.
Are there real examples of data models that actually need to
nest the augment-stmt anywhere and everywhere in the data model,
even inside the 'input' clause for an RPC method definition?

What are the requirements for WG or vendor data model augmentation exactly?


Andy



_______________________________________________
NGO mailing list
NGO@ietf.org
https://www1.ietf.org/mailman/listinfo/ngo