IETF Logo Mail Archive

Re: [netmod] [OPSAWG] Minor change in ietf-access-control-list@2018-02-02.yang

Eliot Lear <lear@cisco.com> Fri, 09 February 2018 09:29 UTC

Return-Path: <lear@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97043126D0C for <netmod@ietfa.amsl.com>; Fri, 9 Feb 2018 01:29:00 -0800 (PST)
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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 KXRdRClLpy1Q for <netmod@ietfa.amsl.com>; Fri, 9 Feb 2018 01:28:59 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3FDB1200E5 for <netmod@ietf.org>; Fri, 9 Feb 2018 01:28:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2912; q=dns/txt; s=iport; t=1518168539; x=1519378139; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=1mk3rXo1nBoq2LRZ/QjceYxn66QRXwDiDGkpszzoAT4=; b=DFpwgZeRt2t0TKyKvVr3xNNlFq0ZXw0WV4+Q4NOpJoi0kbQ87weowO7M uJgzkydPqIBWuiJyp207SxMnyVASYfMgeQH8qYbl3HzXLuFMQdWrbP6PP uWYdPXtvnqSDzV+oQV/lc3OQlPcYXTxuCwSa/3bbXAMzSWZtH4flLYHGq s=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ByAQA+aX1a/xbLJq1dGQEBAQEBAQEBAQEBAQcBAQEBAYUnhA2LGI8zmW0HA4U7AoMLFAECAQEBAQEBAmsohSQBBSNWEAsYKgICVwYNCAEBijGvSIInhQGDeoIKAQEBAQEBAQEBAQEBAQEBAQEBEQ+EfIV9gwWBSYZwgmUFiAOKSZFgCYRngjKFDIN9hV+MOIgGmBCBPDYigVAzGggbFT2CR4JgghdAjSsBAQE
X-IronPort-AV: E=Sophos; i="5.46,482,1511827200"; d="asc'?scan'208"; a="1959223"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Feb 2018 09:28:41 +0000
Received: from [10.61.225.27] ([10.61.225.27]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w199SeCC018854; Fri, 9 Feb 2018 09:28:40 GMT
To: Jan Lindblad <janl@tail-f.com>
Cc: netmod WG <netmod@ietf.org>
References: <CAHiu4JMC6wDc16-Ronz7Ou0Ne9md7acAKJMpU0PN=Bub76tTPQ@mail.gmail.com> <1f32428b-6751-8303-9fc7-ac2c2a92990a@cisco.com> <DC46EA99-94E2-4512-82FA-74683083DFC9@tail-f.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <6ecf354c-42f2-7dc2-f858-7e46f1721be1@cisco.com>
Date: Fri, 09 Feb 2018 10:28:39 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <DC46EA99-94E2-4512-82FA-74683083DFC9@tail-f.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="8AsXGUJQemhGvI074KIEaCxvWLA3eoBW0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/dbltzOVYXH5lC5G9mc77Bl_5ySE>
Subject: Re: [netmod] [OPSAWG] Minor change in ietf-access-control-list@2018-02-02.yang
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Feb 2018 09:29:00 -0000

This may be. bug in OpenDaylight that is being tickled.  Ranga is
chasing it a bit.


On 09.02.18 10:20, Jan Lindblad wrote:
> Eliot,
>
>> In order to compile the published YANG model with OpenDaylight Yangtools I had to make the following change ( diff published file vs. changed file is below ):
>>
>> 583c583
>> <                 path "../../../../../../acl/name";
>> ---
>>>                 path "/access-lists/acl/name";
>> 597c597
>> <                   path "../../../../../../../acl/aces/ace/name";
>> ---
>>>                   path "/access-lists/acl/aces/ace/name";
>>
>> I am not sure (don't have enough YANG experience) to know if the error is with Yangtools or with the published YANG model but I thought I'd send this information to the list just in case.
>>
>> Thank you for your attention.
> Both the old and the new path look valid to me. Even if you can always replace a relative path with an absolute from a YANG validity perspective, changing from relative to absolute paths often *changes the semantics*, so that is not generally safe. In this case, however, they do amount to the same thing (since they both end up going all the way up to the top level container).
>
> /jan
>
>

v2.23.0 | Report a Bug | By Email