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

"Benoit@everything-ops.net" <benoit@everything-ops.net> Sat, 30 May 2026 19:42 UTC

Return-Path: <benoit@everything-ops.net>
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 0C70AF81AFC0 for <netconf@mail2.ietf.org>; Sat, 30 May 2026 12:42:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780170120; bh=TTxZ7YBLeboY8vt6dasiQ1xmup8Zx0LikeFOgyY+gb8=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=Gs/GnrQYoHeFEjNK5048zH96BN+glMEWEXdSIaEQ0kD2k+4ej4w+riebT1v3wpe2M KVKSAElwWdRFlgZbHIK/gvcbAT+o20ADROMEPomN87wDjuDxno7s62OQyzMbL/DH2O 3KKN6YuOyRwYMkQPd6x8VqnlmcANTV42rdlfW7W8=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=everything-ops.net
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 e4Vj0AB_GgCP for <netconf@mail2.ietf.org>; Sat, 30 May 2026 12:41:58 -0700 (PDT)
Received: from smtpout7.mo534.mail-out.ovh.net (smtpout7.mo534.mail-out.ovh.net [54.36.140.178]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0E5F7F81AF97 for <netconf@ietf.org>; Sat, 30 May 2026 12:41:58 -0700 (PDT)
Received: from director3.derp.mail-out.ovh.net (director3.derp.mail-out.ovh.net [152.228.215.222]) by mo534.mail-out.ovh.net (Postfix) with ESMTPS id 4gSVwZ71d9z67JD; Sat, 30 May 2026 19:41:50 +0000 (UTC)
Received: from director3.derp.mail-out.ovh.net (director3.derp.mail-out.ovh.net. [127.0.0.1]) by director3.derp.mail-out.ovh.net (inspect_sender_mail_agent) with SMTP for <mjethanandani@gmail.com>; Sat, 30 May 2026 19:41:50 +0000 (UTC)
Received: from mta7.priv.ovhmail-u1.ea.mail.ovh.net (unknown [10.109.254.159]) by director3.derp.mail-out.ovh.net (Postfix) with ESMTPS id 4gSVwZ5cghz5vMX; Sat, 30 May 2026 19:41:50 +0000 (UTC)
Received: from everything-ops.net (unknown [10.1.6.10]) (Authenticated sender: benoit@everything-ops.net) by mta7.priv.ovhmail-u1.ea.mail.ovh.net (Postfix) with ESMTPSA id 17F03B80D5A; Sat, 30 May 2026 19:41:50 +0000 (UTC)
Authentication-Results: garm.ovh; auth=pass (GARM-102R004b1156843-f9c5-49b9-8071-e1f1bf25b24a, B19900E6C6EE4A019AAD9D1C8938AFB332FAF4C9) smtp.auth=benoit@everything-ops.net
X-OVh-ClientIp: 91.86.233.52
Content-Type: multipart/alternative; boundary="------------sjfo1KnkVkRpntUg93Esjx0t"
Message-ID: <0667a726-6917-4010-9034-c8af9c5f808f@everything-ops.net>
Date: Sat, 30 May 2026 21:41:49 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Thomas.Graf@swisscom.com, andy@yumaworks.com, Mahesh Jethanandani <mjethanandani@gmail.com>
References: <CACvbXWEiQdPr4fEOi4dbkU-jxNiXrJ+SURob-BAh0dO4fx2oPQ@mail.gmail.com> <F5842E72-9E34-454E-BA1F-E90A14EF7CB0@gmail.com> <CABCOCHQUDLVOxuLNDCYEG74Uc9tKSOWM5ysYr7gyhP7A7gvkQw@mail.gmail.com> <ZR1P278MB1170CAF8B0AA186B0A606836890E2@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM> <CABCOCHRkbgqL0eBUdaeUkQMEErqG3ocO7kffta8ot6zyOHz4nw@mail.gmail.com> <ZR1P278MB1170EFA94659857CB1B5FF13890F2@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM>
Content-Language: en-US, fr
From: "Benoit@everything-ops.net" <benoit@everything-ops.net>
In-Reply-To: <ZR1P278MB1170EFA94659857CB1B5FF13890F2@ZR1P278MB1170.CHEP278.PROD.OUTLOOK.COM>
x-ovh-tracer-id: 4430979087566152971
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: -100
X-VR-SPAMCAUSE: dmFkZTFbjMA0mQDXfABkIfNr5+891uVGLN/NZDuiKvn5xTUTtbhO8gM/c2p3RjEuAKoUHAi0d2IYH0+mCG4mg3Fl00Hun6JBN49rpAB6forUAri9rQBJbrUNK0OZHGC+cVLy0bfFYcYi/yrJ2NxpSX7+U0YVC7RfkFnes9Citk5933y5zMQHfZEpnSTX7MQFM1dIS0hrUM2N5iT4RcXOSo3d7sZJlze2HYEZ2MYo+ckmaV/4CieidasiLhnv16xY39GhOkd0Dto0MJwBrdbWpEueZoUSdjbQalfw5lXm/96RtvtAHV2tBDFnqkD7AjPfP3LKa+N6dxUkihZl9Ed16kerZTP9kAYDs2Xky0atduDfiVawf+YJz/CYNeFM3r/ob6neIgI7SREH1ZIzINX+dFtpxLjIEDBQZalpWsVSeGNrDQwwD3Vj1DNppkK2A2qjx8dletIKJ0zTuFJaTsurYxykcSIf7lh72sWTsYijfLG3fzAwlcLTdsSZjYLB1VitAsp7/0+EKxgEA/2UCq8T0ubdiIDeNU4uzp7BayIqbVJs+wnw6R8hn7W5sCaJpa0g5+0uEcvAZpAiWtHvR94IINu6xAyOoPDoLLjb7r2kSy7QJuH48og0cLiXKQHTCvv0lIz4R7K9fzua6aIPdr5Hh7H+afbCyTtWXEuh9AI1uyieiAqotg
DKIM-Signature: a=rsa-sha256; bh=r+/e072fkJ18XWU/lDaNb3QAq4fLUjGwQJc5RpSCwZM=; c=relaxed/relaxed; d=everything-ops.net; h=From; s=ovhmo-selector-1; t=1780170111; v=1; b=KMqUZX1AeitfMdeO1HXChInkhCDNNNnOYs4qWlrzoZ2vNk8U1zCMx0M96BQtH1HgXWCTXKt1 8XkEBKOfK0jlMsv0ZqZHw1hfCjn2DBFMVTuuOhaEJ3FZKqWTuTH5K5GVeRzg03DrGkgf9JbfOI5 cmIr44WPUKVOfhvl7fVOyP39DmlZourBXWEsvl+mYIiyP4eaIR7e0+HfU/dyjGinx8gZJevWcy4 730/LFxE7rfH/t+2bMSiGLKpZuDuvHoqKIBxQgvTJwkw+J+jCq9iAf3CgzksAvJkiDK2c2I39P/ lsFevBrsscxICJJoK/+wrZ0XaDvrb/dOT9bgvrzj58I8A==
Message-ID-Hash: UE6TX7SF6YIY3A426AO24APLSNBP2GXL
X-Message-ID-Hash: UE6TX7SF6YIY3A426AO24APLSNBP2GXL
X-MailFrom: benoit@everything-ops.net
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: 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/Wr9n1dYI1Di5VYu4b5HdV1e2HfI>
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>

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
>     <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
>
>
>             --
>             Per
>
>
>         Mahesh Jethanandani
>
>         mjethanandani@gmail.com
>
>         _______________________________________________
>         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 tonetconf-leave@ietf.org