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, 9 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
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--8AsXGUJQemhGvI074KIEaCxvWLA3eoBW0
Content-Type: multipart/mixed; boundary="GAcUX5iEE3VorNgfd2iVBk6O1pNLJjTm8";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Jan Lindblad <janl@tail-f.com>
Cc: netmod WG <netmod@ietf.org>
Message-ID: <6ecf354c-42f2-7dc2-f858-7e46f1721be1@cisco.com>
Subject: Re: [netmod] [OPSAWG] Minor change in
 ietf-access-control-list@2018-02-02.yang
References: <CAHiu4JMC6wDc16-Ronz7Ou0Ne9md7acAKJMpU0PN=Bub76tTPQ@mail.gmail.com>
 <1f32428b-6751-8303-9fc7-ac2c2a92990a@cisco.com>
 <DC46EA99-94E2-4512-82FA-74683083DFC9@tail-f.com>
In-Reply-To: <DC46EA99-94E2-4512-82FA-74683083DFC9@tail-f.com>

--GAcUX5iEE3VorNgfd2iVBk6O1pNLJjTm8
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

This may be. bug in OpenDaylight that is being tickled.=C2=A0 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 Yangtoo=
ls I had to make the following change ( diff published file vs. changed f=
ile 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 sen=
d 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 le=
vel container).
>
> /jan
>
>



--GAcUX5iEE3VorNgfd2iVBk6O1pNLJjTm8--

--8AsXGUJQemhGvI074KIEaCxvWLA3eoBW0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAlp9acgACgkQh7ZrRtnS
ejME1QgA1aotVgVjbrqBWJ81d+9/8Z/p/pVdt5RBZldrdsljxRJoM6zLkR9qk7Pq
yvevX1OKZ4JIMiBGVDl/3/9tKixdIU2FMIj+y4Id3kekNzpRP7QNKTDl3SpMbM6j
Kstuow6Kk8ZiGJfDxL/AGDX6LWci7nn+qAim5oRDcXX81Pi78chIqSF0ruTCv6v3
vOCgDwhy1KXb6ZxiRXDfj4xkuytMgp0JlxHs3msqzVmir2SceG9JxCiwQ9aiUP+S
3PQm20EIOsnEFKiLhRdgjKdcfD8HgnEcx7Ki5lOlUZ7Gge87shgqWUWe1eD+c9M9
Xj+G9csyTzy9M7JHzLnN1h47ZKZMuQ==
=hXbb
-----END PGP SIGNATURE-----

--8AsXGUJQemhGvI074KIEaCxvWLA3eoBW0--