Return-Path: 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 B0F61120B33 for ; Wed, 9 Oct 2019 14:30:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 LmCzzUiAdy93 for ; Wed, 9 Oct 2019 14:30:05 -0700 (PDT) Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0058412084F for ; Wed, 9 Oct 2019 14:30:04 -0700 (PDT) Received: by mail-lj1-x232.google.com with SMTP id b20so3994049ljj.5 for ; Wed, 09 Oct 2019 14:30:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CMZWLlHm2SVIj9eMxxBJ/e37KXzVa7pgZrrQzuep9bc=; b=c87mgOR+TGVNOEzB83+isqnstFV/EFtYzy/JbnmPBiuVm6L3wlO/ynbNF0cTHF1TFH nmx0osMeTI9ra5FUCQ+MSzEceMz6ZllmGySL60Ul7cvmkUrs4zwkaP9tXNewUvxceoBh aNKj2FPdZtSUSVL0PBhoFfiJmfZliNdOc+QIzXGUOUKyn73nro+WNeM9ORhBDofRk3i0 MLgXxeyLs3eiyiOFZibJfsU6Xo1kf+mpi0uP8aYMMVtFEPdraxZ5DOArnwsSpW45QWGm MVsPk3HXtpB1BdKq+ndsweAbg4WzIKvdFTJhvfnn5UqCz9h+OcfRVj0EW7cEr11Ktia8 6HEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CMZWLlHm2SVIj9eMxxBJ/e37KXzVa7pgZrrQzuep9bc=; b=hj6rAmICld/w4t7JDBfmI0PUEBV0cMUeAAALkmfjm2xjOx+VvFuEUQnePvtcXYPn0C DzloO/vwQLVivKPGYS02uMXLo1KrWSteaDhWuA4brygC1AVqywNYPzyrV9utLFITuxpw IGFPamxIHSNZFuWHGUEvFOaN6/QDGNQG/brjmjQOyRmhS+pyct2QZgQ1aQ2KutqkweXb 3o3LDkJB4B6ERPywXh0NWBH2te017SQDP5tZ7jyQqIzuQBRUGKAxMoNe6MXVXIcEHn6g I50sHFqpoC2vlZV7Sg/lWgwkp9wePuqiy7FLIgioVxSmgYEBrieIRbF8a2kN/az7CwUK X+UA== X-Gm-Message-State: APjAAAVRnpjQmx2dBaoklDntNlq3Vub7moLpwOn2wNrxA6j4mGXFs0xn tjCIYxFfiqEkBaGaHIwlMZQWjmzH7X4jQMDRAoAE3w== X-Google-Smtp-Source: APXvYqw5eZthI17ggIB60YmQSLi289Hg78SaRndjRf02lmALvVKCxHcg6an+OAqO5Vwn5+jgn0hgLdASfdracfCOtoM= X-Received: by 2002:a2e:2bc8:: with SMTP id r69mr3754284ljr.147.1570656602938; Wed, 09 Oct 2019 14:30:02 -0700 (PDT) MIME-Version: 1.0 References: <392C0EBE-FAAA-48DE-A3A1-C94A1E21AE59@gmail.com> In-Reply-To: <392C0EBE-FAAA-48DE-A3A1-C94A1E21AE59@gmail.com> From: Andy Bierman Date: Wed, 9 Oct 2019 14:29:51 -0700 Message-ID: To: Mahesh Jethanandani Cc: =?UTF-8?Q?Bal=C3=A1zs_Lengyel?= , "netmod@ietf.org" Content-Type: multipart/alternative; boundary="000000000000e1f36a059480fc32" Archived-At: Subject: Re: [netmod] PYANG refine fault ? X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2019 21:30:08 -0000 --000000000000e1f36a059480fc32 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, The YANG looks valid. yangdump-pro reports 1 warning: Warning: Revision date in the future (2019-10-10) ietf-notification-capabilities@2019-10-10.yang:90.3: warning(1021): revision date in the future *** /home/andy/Desktop/ietf-notification-capabilities@2019-10-10.yang *** 0 Errors, 1 Warnings Andy On Wed, Oct 9, 2019 at 2:14 PM Mahesh Jethanandani wrote: > Hi Balasz, > > In general support of unions is poor across the tool sets that I have > used. It does not help that yanglint gives a completely different error. > > I did try yanger, and that did not result in an error. > > The other option is to move the default statement inside the grouping, > which seems to make the error go away. > > Cheers. > > On Oct 9, 2019, at 8:01 AM, Bal=C3=A1zs Lengyel < > balazs.lengyel=3D40ericsson.com@dmarc.ietf.org> wrote: > > Hello, > I was trying to validate the attached model. However pyang keeps > complaining about refining a default for a leaf-list: > > ietf-notification-capabilities@2019-10-10.yang:184: error: "leaf-list" > node "ietf-notification-capabilities::supported-excluded-change-type" > cannot be refined with "default" > > > Why? According to https://tools.ietf.org/html/rfc7950#section-7.13.2 =E2= =80=9CA leaf-list node may get a set of default values ...=E2=80=9D > > . > Confdc accepts this. Could this be a bug in pyang ? > Regards Balazs > > -- > Balazs Lengyel Senior Specialist > Ericsson Hungary Ltd. > Mobile: +36-70-330-7909 email: Balazs.Lengyel@ericsson.com > > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod > > > Mahesh Jethanandani > mjethanandani@gmail.com > > > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod > --000000000000e1f36a059480fc32 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

The YANG looks valid.
yan= gdump-pro reports 1 warning:


Warnin= g: Revision date in the future (2019-10-10)
ietf-notification-capabiliti= es@2019-10-10.yang:90.3: warning(1021): revision date in the future

= *** /home/andy/Desktop/ietf-notification-capabilities@2019-10-10.yang
**= * 0 Errors, 1 Warnings

Andy

On Wed, O= ct 9, 2019 at 2:14 PM Mahesh Jethanandani <mjethanandani@gmail.com> wrote:
Hi Balasz,

In general support of unions is poor acro= ss the tool sets that I have used. It does not help that yanglint gives a c= ompletely different error.

I did try yanger, and t= hat did not result in an error.

The other option i= s to move the default statement inside the grouping, which seems to make th= e error go away.

Cheers.

On Oct 9, 2019, at 8:01 AM, Bal=C3=A1zs Lengyel &l= t;balazs.lengyel=3D40ericsson.com@dmarc.ietf.org> wrote:
Hello,
I was trying to validate the attached model. However pyang keeps compl= aining about refining a default for a leaf-list:
=C2=A0
ietf-notification-capabilities@2019-10-10.yang:184: error: = "leaf-list" node "ietf-notification-capabilities::supported-= excluded-change-type" cannot be refined with "default"
=C2=A0
Why? According t=
o https://t=
ools.ietf.org/html/rfc7950#section-7.13.2 =E2=80=9CA leaf-list node may=
 get a set of default values ...=E2=80=9D
.
Confdc accepts this. Could this be a bug= in pyang ?
Regards Balazs
=
=C2=A0
--=C2=A0<= u>
Balazs Lengyel=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= Senior Specialist=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= Ericsson Hungary Ltd.=C2=A0
Mobi= le: +36-70-330-7909=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 email:=C2=A0Balazs.Lengyel@ericsson.com
<= div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,san= s-serif">=C2=A0
<ietf-notification-capabilities@2019-10-10.yang>______________________________________= _________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
=

Mahesh Jethanandani



_______________________________________________
netmod mailing list
netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
--000000000000e1f36a059480fc32--