Re: [netconf] YANG Push module errors

Michal Vaško <mvasko@cesnet.cz> Fri, 02 April 2021 19:49 UTC

Return-Path: <mvasko@cesnet.cz>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 395C53A2141; Fri, 2 Apr 2021 12:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cesnet.cz
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 qrf9f33TK5Gg; Fri, 2 Apr 2021 12:49:30 -0700 (PDT)
Received: from kalendar.cesnet.cz (kalendar.cesnet.cz [IPv6:2001:718:1:1f:50:56ff:feee:34]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0750A3A213C; Fri, 2 Apr 2021 12:49:29 -0700 (PDT)
Received: by kalendar.cesnet.cz (Postfix, from userid 110) id 18C2A60088; Fri, 2 Apr 2021 21:49:25 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=kalendar; t=1617392965; bh=9oemDNenWsWvOamzYnrH4Sl9xT/sqxZ5MLVCZhKvIow=; h=From:In-Reply-To:Date:Cc:To:Subject; b=03UPHwVBvU4VoXQlWgTAUsGfukckahcotd4/gwARcFbCfVeAf2g02djViYHN/HAxj KS8xIMmF9yJ0wx5FgQslZPl7RnZH6QFsHN7Xq/RhuaseHR2rYFFRezpnqwuarZZofY XBuqy2DyVJONvXSO32zlPiNMZRh9GWRXHAfoGCxs=
From: =?utf-8?q?Michal_Va=C5=A1ko?= <mvasko@cesnet.cz>
In-Reply-To: <BL0PR11MB31226974AEC11A5936BA40C9A17A9@BL0PR11MB3122.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
X-Forward: 84.42.188.124
Date: Fri, 02 Apr 2021 21:49:25 +0200
Cc: "netconf" <netconf@ietf.org>, "netmod" <netmod@ietf.org>
To: "Eric Voit (evoit)" <evoit@cisco.com>
MIME-Version: 1.0
Message-ID: <5830-60677580-9-1569b540@260964559>
User-Agent: SOGoMail 5.0.1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/c0Z7NoDsWZ3Iai8n32dxFHVwLcM>
Subject: Re: [netconf] =?utf-8?q?YANG_Push_module_errors?=
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2021 19:49:35 -0000

Hi Eric,

thanks for the answer.

On Friday, April 02, 2021 15:43 CEST, "Eric Voit (evoit)" <evoit@cisco.com> wrote: 
 
> Hi Michal,
> 
> This sounds like a tooling issue to me.  I would expect that any augments
> would inherit the conditional nature of anything augmented.  

Perhaps, but there is nothing in the specification to hint this. On the contrary, leafrefs, for example, explicitly require to be conditional on the same set of if-features than their targets. But you are right, there is no such requirements for augments. Still, if the feature is disabled and the augment should be applied, since its target does not technically exist in the schema, it cannot be found. That is the error our tools currently produce.

> If you disagree, perhaps a thread to the netmod alias would get you an
> 'official' answer on the proper behavior.

I have sent the email to "netconf" because that is WG that published it but no harm in adding a copy for "netmod".

> Eric
> 
> > -----Original Message-----
> > From: netconf <netconf-bounces@ietf.org> On Behalf Of Michal Vaško
> > Sent: Thursday, April 1, 2021 11:14 AM
> > To: netconf <netconf@ietf.org>
> > Subject: [netconf] YANG Push module errors
> > 
> > Hi,
> > 
> > we are led to believe there is an error in the ietf-yang-push module
> published in
> > RFC 8641 but I wanted to discuss it here before submitting an errata.
> There are 2
> > augments [1] on a notification that is conditional on "configured" feature
> but
> > these 2 augments are not conditional. Having this feature disabled, we
> were not
> > able to load this module into our tools. Does anyone disagree with this or
> with
> > submitting an errata?
> > 
> > Regards,
> > Michal
> > 
> > [1] https://tools.ietf.org/html/rfc8641#page-48 and the next page
> > 
> > _______________________________________________
> > netconf mailing list
> > netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf