[netconf] Re: yang-library-augmentedby: Mix of deprecated/current in leaf-list

Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 01 June 2026 11:10 UTC

Return-Path: <mjethanandani@gmail.com>
X-Original-To: netconf@mail2.ietf.org
Delivered-To: netconf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id C4AFBF89DC7B for <netconf@mail2.ietf.org>; Mon, 1 Jun 2026 04:10:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780312244; bh=TSuh1uAg/lk0As/av53qoHBzoSvK2VIUuJCoNDVzyoE=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=Yd0abXRliAHKfTBNdYjm10SdvZqQFN3LLGQsjCChO0m6wViZxR7exA1dIgV5mYPCo JLttVY8ZZ0b59kAd3GMQZ/jpWoR/N1h6hyU3/6PqKb81HKRE10YdSTBdb3cY41OuQp zuaR/1OWoTv1a01GIIO3kyrBbnb2uCkYBP0heWkk=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.206
X-Spam-Level:
X-Spam-Status: No, score=-1.206 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4cZIw_3p23y4 for <netconf@mail2.ietf.org>; Mon, 1 Jun 2026 04:10:43 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D8CC5F89DC16 for <netconf@ietf.org>; Mon, 1 Jun 2026 04:10:29 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id d75a77b69052e-5174a0beffcso15581341cf.1 for <netconf@ietf.org>; Mon, 01 Jun 2026 04:10:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1780312229; x=1780917029; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=ir+V8nf4NOMz4qfIOuQIwTzH+vUlX7CCW9MvyVGRMNA=; b=NOnizCwIwDbSzEAGoHN+RvIkmYTG3Seqmjbj7FWP0Cc/z5byn3C2n/NSlW9hwoUj+a u5GfwoAR4BzDvvZjQNp5/JbPIpnjsHjKNtbV8lwDavIIph2uoCcTQKo1pt8qjDwQmCYq iT96saSRpgx3xaWug3O1r7MU63tMXxIh7WORq33k68EroVwtPirzfiT4VFastQjYshlp PD9yErb8ejj3gAO1V9wApM0AivfrQ/QIhOMvYZJL9WefhI9HHlZrsijD/2BDyIBVx84s JBgqDo8vshpvZjf+y74pGJwQy9WwV5FHUInN0CSCL97/Kb+dXrD5L+oFImFqWJ8iNXMe OLUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1780312229; x=1780917029; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-gg:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=ir+V8nf4NOMz4qfIOuQIwTzH+vUlX7CCW9MvyVGRMNA=; b=MoGIRQ0IN5G8pfwWnxaFpmVJZDXQYJ+cg/Dzh4n87JgXKsPGYcyxjGSDGwqSXaeINL RiYYhmZWcwFNGRRAYzorQk6Z5+g0iY8fpKcXHNh4uHRsd1EJHC34XClF/vcK2mBUGpbl 9CuzIZ12j+wuF4C3Om42s6QM8IRt0rcNdccEXGjR0Gl6lbn7vAPfxADm1kpBH0PRV1u/ vK/VWf5d24a5EuujnWvizBXVS46osFccqfF254mihJ9x/IKoGcKy3tS2kicz3CFNWXfk hsjKxnAVXs5QJZcwmGvmpsa49a6jroK2IxF1OGIhceOfPfqhBv+3mvZuHhlE14cD49hd dSCg==
X-Forwarded-Encrypted: i=1; AFNElJ+z3xj97EgsJSu7H4DDMiKAar1xb9QDxLrhc59alhm5sBGB3EkBWvlxClD23eRulSqD3gjMBwQc@ietf.org
X-Gm-Message-State: AOJu0YwY0b3efV0Ln3h5tpWojo9ejeSxgZS2D9ckE+Cc8IijhVLksfSw CeRHyvvnZbzeKoS0pAhpLULzgayzXQDlNm7bmleRZNgzyW0fFeXl+1FU
X-Gm-Gg: Acq92OHqPO8qmszZJ78nKW5ke5izZvbCicqVQH7LayHpmUaWHgES0zNqlmKN/X5yYBH fNVje5jcaf0MN5rVzVhoRY6IkPtxN6JabZkCkVfHXnclvhQDUSL8swp5T+rAg1eorPPFDDGM0x2 DpIbreXTyDBRMRPzM4DUauD8Mh2P6pVmLszAaNnWb5EtvnoLuM3lWfYv3vhSDDv5dfDbfceLGPC ursqq9qjjISIJlpLJeoTB/2CWdw8Trj6UWbnIY00g6o75zjjFxPQpMogX3ZUz5krd08m4YW9aoG u6BoxHrGIXR08c4P6SDqJ0mkmc8+4jOgo6DQrFsDm5W0guLQ5EI/JTemiCOQHwIPF2q6XYT6mVV 6lmyjZ2Ni64iC6Ka9xeylAWzQ/JgOthAmrEx9Emebb8PHBs2f/hX2n+4PDXXExIu2OrR1SDZFBB 8IzsVujUH5X/4uhAfbx7RBDbGyx95td3QT5Sc1wEunB8dMJKfPOPlhIF1Yq/uMh/6ryQ==
X-Received: by 2002:a05:622a:d0f:b0:516:e36f:e18a with SMTP id d75a77b69052e-5173a6e5ccdmr141469241cf.2.1780312229180; Mon, 01 Jun 2026 04:10:29 -0700 (PDT)
Received: from smtpclient.apple ([2607:fb91:1c0d:d2ae:5049:dce6:34eb:e260]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-51741b05915sm53270121cf.1.2026.06.01.04.10.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Jun 2026 04:10:28 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-9C808109-71A6-4D84-A7E5-57CD23AD74A9"
Content-Transfer-Encoding: 7bit
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 01 Jun 2026 07:10:17 -0400
Message-Id: <D3D52E18-19FB-43AF-A282-DA671D526C9E@gmail.com>
References: <0667a726-6917-4010-9034-c8af9c5f808f@everything-ops.net>
In-Reply-To: <0667a726-6917-4010-9034-c8af9c5f808f@everything-ops.net>
To: benoit@everything-ops.net
X-Mailer: iPad Mail (22H352)
Message-ID-Hash: TJ3QLNMA5EDEHPX6J25SFZUDCJR3Z65Z
X-Message-ID-Hash: TJ3QLNMA5EDEHPX6J25SFZUDCJR3Z65Z
X-MailFrom: mjethanandani@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Thomas.Graf@swisscom.com, netconf@ietf.org, draft-ietf-netconf-yang-library-augmentedby@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [netconf] Re: yang-library-augmentedby: Mix of deprecated/current in leaf-list
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/eI312nsAMTty-vq5UQv_DJwdLY0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>

Hi Benoit/Chairs,

My suggestion would be for the chairs of NETCONF to do a poll of the WG to see if the WG has consensus around the solution suggested by Per.

Thanks.

Mahesh Jethanandani

On May 30, 2026, at 3:41 PM, benoit@everything-ops.net wrote:

 Dear AD, chairs,

What do we do from here?

Regards, Benoit

On 22/05/2026 07:30, Thomas.Graf@swisscom.com wrote:

Dear Andy,

 

Thanks.

 

AB> The new /yang-library subtree is to support NMDA, which is rarely used.

 

To which implementation are you refering to?

 

5 years ago I would have agreed with you. I am aware that the following network operating systems have updated their implementations a while ago:

 

Cisco IOS XR, XE and NX-OS

Juniper JunOS

Nokia SR-OS

Huawei VRP (OLT, IP and SDWAN)

Nokia SR-OS

Arista EOS

 

Since usually network operating systems have a lifecycle of 1-3 years, having network operating systems which still doesn't support RFC 8525 are rare in Swisscom's network and if there are, they are already planned to be upgraded.

 

I have seen network operating system implementations where the development time to upgrade from YANG Library RFC 7895 to 8525 took literally just a few days. I am aware of 4 network operating system implementations of draft-ietf-netconf-yang-library-augmentedby. All of them chose to augment yang-library on RFC 8525 based implementations.

 

On the YANG library side which the OSS systems are using. We did a comprehensive feature comparison between libyang, yangtools and yangkit. From what we observed there is that today, only libyang out of the 3 has YANG library support. In yangkit the YANG library support is under development where in yangtools we are considering code contribution. RFC 7895 is no longer considered there. From my personal experience, I am also aware that ncclient and NSO is using RFC 8525 NMDA yang-library.

 

Best wishes

Thomas

 

From: Andy Bierman <andy@yumaworks.com>
Sent: Thursday, May 21, 2026 6:43 PM
To: Graf Thomas, SCS-INI-NET-VNC-E2E <Thomas.Graf@swisscom.com>
Cc: mjethanandani@gmail.com; netconf@ietf.org; draft-ietf-netconf-yang-library-augmentedby@ietf.org
Subject: Re: [netconf] Re: yang-library-augmentedby: Mix of deprecated/current in leaf-list

 


Be aware: This is an external email.

 

 

 

On Thu, May 21, 2026 at 8:21 AM <Thomas.Graf@swisscom.com> wrote:

Dear Andy,

 

Reading https://datatracker.ietf.org/doc/html/rfc7950#section-7.21.2" target="_blank" rel="nofollow">https://datatracker.ietf.org/doc/html/rfc7950#section-7.21.2

 

   o  "deprecated" indicates an obsolete definition, but it permits

      new/continued implementation in order to foster interoperability

      with older/existing implementations.

 

   If a definition is "current", it MUST NOT reference a "deprecated" or

   "obsolete" definition within the same module.

 

I believe that what RFC 7950 meant to say it that when something is deprecated, it should not be extended anymore because it is deprecated.

 

Even though we can trick the compiler with a leaf-list, I don't thing we are acting in the spirit of RFC 7950 and RFC 8525 authors.

 

Therefore I believe the best option is to remove

 

  augment "/yanglib:modules-state/yanglib:module" {

    status deprecated;

    description

      "Adds Augmented-by leaf-list to the list of modules of a module set";

    uses augmented-by;

  }

 

from ietf-yang-library-augmentedby. As an implementor who implements ietf-yang-library-augmentedby, I believe it is a no brainer to upgrade ietf-yang-library to RFC 8525 if it is not already done so. RFC 8525 has been published 7 years ago.

 

 

 

I don't care if the /modules-state augments is removed.

 

The new /yang-library subtree is to support NMDA, which is rarely used.

The added complexity for the client is non-trivial.

A non-NMDA server has no reason to update to RFC 8525.

 

Best wishes

Thomas

 

 

Andy

 

 

From: Andy Bierman <andy@yumaworks.com>
Sent: Friday, May 15, 2026 6:09 PM
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Cc: NETCONF WG <netconf@ietf.org>; draft-ietf-netconf-yang-library-augmentedby@ietf.org
Subject: [netconf] Re: yang-library-augmentedby: Mix of deprecated/current in leaf-list

 


Be aware: This is an external email.

 

 

 

On Thu, May 14, 2026 at 12:41 PM Mahesh Jethanandani <mjethanandani@gmail.com> wrote:

Hi WG,

 

The document is currently in the RFC Editor queue and we need to decide fairly quickly what to do with this “errata”.

 

The suggestion from Per is small and doable with where the document is, if the WG agrees that the change is needed. 

 

 

The change looks OK.

It is unfortunate that the status-stmt has so many issues.

 

This does violate a MUST NOT rule, so it should be fixed.

However, the accepted meaning of 'deprecated' is that the schema node is implemented, but

it may be removed in a future module revision.   The rule about 'current' MUST NOT reference 'deprecated'

is therefore ignored.  Since 'obsolete' means the node is not implemented, any reference to 'obsolete' will cause an error.

 

Thanks.

 

Andy

 

 

 

On May 13, 2026, at 8:13 AM, Per Andersson <per.ietf@ionio.se> wrote:

 

Hi,

The ietf-yang-library-augmentedby.yang has the following
construct:

 grouping augmented-by {
   leaf-list augmented-by {
     type leafref {
       path "../../yanglib:module/yanglib:name";
     }
 }

 augment "/yanglib:modules-state/yanglib:module" {
   status deprecated;
   uses augmented-by;
 }

Trying to compile this module yields a warning because:

* the "module" container is deprecated,
* the "augmented-by" leaf-list is implicitly current
* the leafref "yanglib:name" is deprecated

This is not allowed per RFC 7950 Section 7.21.2:

  If a definition is "current",  it MUST NOT reference a
  "deprecated" or "obsolete" definition within the same
  module.

The issue is that the status statement is not inherited,
see yang-next issue #27 [0].


I think we should create YANG modules that follow the
specifications.

Suggest that the grouping is rolled out in the module,
and stated explicitly in both augments:

 augment "/yanglib:yang-library/yanglib:module-set/yanglib:module" {
   leaf-list augmented-by {
     type leafref {
       path "../../yanglib:module/yanglib:name";
     }
 }

 augment "/yanglib:modules-state/yanglib:module" {
   status deprecated;
   leaf-list augmented-by {
     status deprecated;
     type leafref {
       path "../../yanglib:module/yanglib:name";
     }
 }

Not as elegant as the module is defined now, but at least
the compiler doesn't complain and we follow YANG.


[0] https://github.com/netmod-wg/yang-next/issues/27" target="_blank" class="moz-txt-link-freetext" rel="nofollow">https://github.com/netmod-wg/yang-next/issues/27


--
Per

 


Mahesh Jethanandani

 

 

 

 

 

_______________________________________________
netconf mailing list -- netconf@ietf.org
To unsubscribe send an email to netconf-leave@ietf.org


_______________________________________________
netconf mailing list -- netconf@ietf.org
To unsubscribe send an email to netconf-leave@ietf.org