[Rtg-yang-coord] Augment target path
"Acee Lindem (acee)" <acee@cisco.com> Wed, 01 April 2015 14:59 UTC
Return-Path: <acee@cisco.com>
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 015CF1ACD45 for <rtg-yang-coord@ietfa.amsl.com>; Wed, 1 Apr 2015 07:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 fWVDCq_wgAHy for <rtg-yang-coord@ietfa.amsl.com>; Wed, 1 Apr 2015 07:59:32 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A37D1ACD3C for <rtg-yang-coord@ietf.org>; Wed, 1 Apr 2015 07:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=810; q=dns/txt; s=iport; t=1427900372; x=1429109972; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=rRR+4Zj0qmt875QOX2RNLCQRDx5ApCTYHdq52+hynPg=; b=PDF6IP4x1hnckDZexefBdpjhGwas6OkyAQZmKCUwCLp82KJKWzXcop15 GsmbeRQmMl/42+rzYU/gU3GwpgF4up/uAxlAHFl05MfvJbyub3VicavyW pcGqYTalnhh6zp4JHA5LqRVgrqw5I9CTLtBR+Wq9jpizAIZ15qtbdh6We o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALBQBuBxxV/4QNJK1cgwZSXAWDEMJFhhGBJEwBAQEBAQF9hBsjEVcBIgImAgQwFRIEHIgmDaV7j0yZMCyBIZFvgUUFkGOJdpQ+IoNubwGBQ38BAQE
X-IronPort-AV: E=Sophos;i="5.11,504,1422921600"; d="scan'208";a="405288024"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-9.cisco.com with ESMTP; 01 Apr 2015 14:59:31 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t31ExVBo022481 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtg-yang-coord@ietf.org>; Wed, 1 Apr 2015 14:59:31 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.236]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Wed, 1 Apr 2015 09:59:31 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Routing YANG <rtg-yang-coord@ietf.org>
Thread-Topic: Augment target path
Thread-Index: AQHQbIx0dLJIH2CQzUmiEGTR+JZhGA==
Date: Wed, 01 Apr 2015 14:59:30 +0000
Message-ID: <D141801A.14361%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4D6C66368DC255449BEB88ED8975523F@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/hqRjjJagYwA7FTFxL_1ivMV_sjk>
Subject: [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 14:59:36 -0000
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] Augment target path Acee Lindem (acee)
- Re: [Rtg-yang-coord] Augment target path Giles Heron
- Re: [Rtg-yang-coord] Augment target path Acee Lindem (acee)