Re: [Rtg-yang-coord] Augment target path

Giles Heron <giles@layerfree.net> Wed, 01 April 2015 15:43 UTC

Return-Path: <giles@layerfree.net>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00B371ACE21 for <rtg-yang-coord@ietfa.amsl.com>; Wed, 1 Apr 2015 08:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5Vy2u_HneAm for <rtg-yang-coord@ietfa.amsl.com>; Wed, 1 Apr 2015 08:43:40 -0700 (PDT)
Received: from layerfree.net (heronab1.miniserver.com [77.73.2.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C7AD1ACDEF for <rtg-yang-coord@ietf.org>; Wed, 1 Apr 2015 08:43:36 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=128.107.241.181;
Received: from [10.24.102.23] (unverified [128.107.241.181]) by layerfree.net (SurgeMail 6.5a) with ESMTP (TLS) id 14012-1293857 for multiple; Wed, 01 Apr 2015 15:43:00 +0000
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Giles Heron <giles@layerfree.net>
In-Reply-To: <D141801A.14361%acee@cisco.com>
Date: Wed, 01 Apr 2015 16:43:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1CC500B8-012E-4A82-853B-E2269F15990B@layerfree.net>
References: <D141801A.14361%acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Authenticated-User: giles@layerfree.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/PB5eMTxuW8f_GdxhTzcBhsVTfaU>
Cc: Routing YANG <rtg-yang-coord@ietf.org>
Subject: Re: [Rtg-yang-coord] Augment target path
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 15:43:42 -0000

Hi Acee,

I don't think you can augment a grouping (as groupings don't actually exist in the data tree).

From RFC6020 section 7.15: "The target node MUST be either a container, list, choice, case, input, output, or notification node."

can you try:

augment "/key-chain:key-chains/key-chain:key/key-chain:crypto-algorithm/key-chain:algorithm" {...

Giles

On 1 Apr 2015, at 15:59, Acee Lindem (acee) <acee@cisco.com> wrote:

> I’m trying to test out augmentation and am not able to get pyang to find
> the target node. What am I missing? I’m trying to augment the crypto
> algorithm types in 
> http://www.ietf.org/id/draft-acee-rtg-yang-key-chain-03.txt
> 
> I tried both augmenting the “choice” in the “grouping”
> 
> augment “/key-chain:crypto-algorithm-types/key-chain:algorithm” { …
> 
> And augmenting the “choice” in the “container" using the “grouping”.
> 
> augment “/key-chain:crypto-algorithm/key-chain:algorithm” { …
> 
> In both cases, it wasn’t found.
> 
> Thanks,
> Acee 
> 
> _______________________________________________
> Rtg-yang-coord mailing list
> Rtg-yang-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/rtg-yang-coord