Return-Path: <andy@yumaworks.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 2C4B9F8D1575
	for <netconf@mail2.ietf.org>; Mon,  1 Jun 2026 11:22:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1780338145; bh=qCfIsVzwjqxI+1oQQ2Hc+ibnX1oE7zPkw7XS3iIQf/g=;
	h=References:In-Reply-To:From:Date:Subject:To:Cc;
	b=KAuok1dvC7wrJjjkig3OQ31UhvAxb6LHRz2VEaAs7ZRnDePBgQnbyg+QyHMTlns5G
	 ppHrvCM2FbshmjrOnPydu6RrDZjtnvOKKX4jgcw1xIH1QFyjmkCpfU4PDo+YwgSWRt
	 WwxraDCfBLnIO+ZVe5QDNG1rdJyaJ//GH86wFC8U=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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=yumaworks.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 CBl7zmn2YQER for <netconf@mail2.ietf.org>;
	Mon,  1 Jun 2026 11:22:22 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com
 [IPv6:2a00:1450:4864:20::22d])
	(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 BF38EF8D1565
	for <netconf@ietf.org>; Mon,  1 Jun 2026 11:22:22 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id
 38308e7fff4ca-3967701fc3cso2849481fa.0
        for <netconf@ietf.org>; Mon, 01 Jun 2026 11:22:22 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1780338136; cv=none;
        d=google.com; s=arc-20240605;
        b=QlBo8b2SMHwSs4NrUfWa5aZ/20k+n28fgLve7D9S1u7US76rNFXq/V+MuBIcOeu6JD
         jk2dvaEt2fFiBRXzwKkpwHvsqYH293uSHgsPZIQwI60ILPGCPpqgcI8kv4b63adc0gz1
         O7RuYknZws6HB1dkZ6NA+AM/ixaY+BFagF0pXV+sQv1gsWUq1p7mmF86AWQU/kNvWWx1
         5HS+NUXGACKG3UfkeiCYyrOoKlrU7/jWdeibwesIs2F7LGTFcPrlCRaLUQvKuCPeaF6t
         SlI76E6DfZURfez2QAVQpI01XZQqkiQHhxii44VkUcUXDEUQOTCycZtmnSGSpyX3AVME
         kCQA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
 s=arc-20240605;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:dkim-signature;
        bh=OSEs8OL5BcvYtU6eAEP9VRT4KaMnDMoO7lP56APtknA=;
        fh=amZweZGRetuuP7zjcWCA9FrMFddkwE4ZUyjf8RefEM8=;
        b=dEiAHiA6h/A2nR6DKSNIiMhtqPShsZKBDrXo69d0/ujg/OB6ukL680XPIFlHjO+gxt
         pGsnDJpcGDTYZQtEb5VYIP0wr3FdGyAompHGkNdKl5OZvR2WRr6t69Kb4HmWP+F/QIBn
         whTbAesD6qS6NQLz+SwlFCCV7e0JpgMI+5Y2vYTLTmZAcyo0uxSRJOItRv+86CkosTLp
         0n/DOe+YRMAxkq+5AmB4qo1TgW3Rp+Mgiu177MbM4enLC1tqP3r11SLPCUrEH8p5/Xiy
         6mCIClC0fdLnSkmaLsngOorrlz+lL+Vppb2aNHedvshoj97xypZFjvCQrJI8n8sCB5z7
         Ye0w==;
        darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=yumaworks.com; s=google; t=1780338136; x=1780942936; darn=ietf.org;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:from:to:cc:subject:date:message-id:reply-to;
        bh=OSEs8OL5BcvYtU6eAEP9VRT4KaMnDMoO7lP56APtknA=;
        b=beJJdA+pOsqgyqH6BOd7ywQyXA9pFYzkcBmTTPYQW+NX9jfeXQHaTTuQZw+uJxfv6h
         KmgUPijw/TzD1hWGlaIZxA/5pMBRHeLjQn6Em4pVumZEQxiULdcRl9NrD4mwjwV+WdZO
         gpbvwqYstPSq0NyCPoqZxQWyx22AFpQeYSAOvwnpT1EUmR3Rbn+jmDyZxxVb0iKhUgLS
         jaccmTWdw99tFVBV0tfCsbtlqLq0pTMpY60VBYdzbZqgGL0JInI2C1aumMXCD+ciqykp
         scejtL4qNc1wMnd5DCvPbleF6T+pngaV/v7vYTJ4upJMxKR3VXQ7cGc6votVQ8feBeC+
         ccmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20251104; t=1780338136; x=1780942936;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date
         :message-id:reply-to;
        bh=OSEs8OL5BcvYtU6eAEP9VRT4KaMnDMoO7lP56APtknA=;
        b=MNX3vnxXnlL3BPZio6tpSunAxm4Ek7HhPPoy6sIkQe790OIHaJ4W0TqaoxjSc3U9Uh
         zpV0P6LUHNYlGD05yWErZYakWzz6M3yY/OMvhnq/68aJiVHOphSik1NNgOHO4nZmYSKB
         mEnwk0dmwvNTvXIvVikUagqTUd8f0BNAGvpyQzVn1na2Kfe/YpMM1s2GJc8ruv9KV1B/
         45jD7daGI6mGXKRyzFeuKyZsWHpH6TwECBBZCRtfQpk7kv+rqczQ+V+3HS+JM+zaPUt5
         uyUC9fWdVQpRW/eHzkPcT+KO7zqY3g80jcrHjbtfCRaRQTLW07/3m21VSv9w8FIDCQCo
         MwCw==
X-Forwarded-Encrypted: i=1;
 AFNElJ+gUSGwMC7Wi8Tsa3YRhgYGgKjykrIBU+ezghTYE3/6CixwvdKKATTSQnLDBS8K6fSGZ0IBpZaH@ietf.org
X-Gm-Message-State: AOJu0Yx1d3Bm8vCVBK2X7j7oDX/wfeTJf9gloPuZseejFKNUm5k9TluH
	qRQ2QvvBhbGORieqPG1JOij2BG+auhCHBwyiuOGXjQnehea2IQwshzUJTUN8elH0gkFevuYA22I
	SEPWhPY8ZmqDGTKC82HyyC723yfnSyB3E/48WbhYGnw==
X-Gm-Gg: Acq92OFWXK5s91FGMNgu7AXhVKi32JI992muUtdyDVNGcul27uhqd3DNj24zUMKcoAS
	kCX3nlF9Dd7ngQuW6A8feX7oBOfn/48Idg0WQKNR0+SLC/LACLqIyz8rAE/OGMpGktMS5fY4vLj
	ctnxWaT9no9iIcEi5u3ogeoZ1f92p4WB5NfL4519g/Fq31bzpGGmXDw19tQiS8f/qfMpVR2iRRa
	B9EykR3JeONEHgLy4oqzWvbHIqu5sqk5pTgshSh0tNfh5R+QOCZ+URuBaRXKGpm2g59Dm5penwR
	j6poE3e3QSMQVsaF
X-Received: by 2002:a2e:be9d:0:b0:396:7953:b316 with SMTP id
 38308e7fff4ca-3967953b51fmr12861781fa.1.1780338135543; Mon, 01 Jun 2026
 11:22:15 -0700 (PDT)
MIME-Version: 1.0
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>
 <CACvbXWF6qT3SGRJmH-mRm0jTmPJp-9o4oLZCpBgKk-NQx304JA@mail.gmail.com>
In-Reply-To: 
 <CACvbXWF6qT3SGRJmH-mRm0jTmPJp-9o4oLZCpBgKk-NQx304JA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 1 Jun 2026 11:22:02 -0700
X-Gm-Features: AVHnY4InRdcGDwOlRlVvReFpgYfzDaPyqaZ8ay3vfgFagNJPqPRhif7XG8nkbvM
Message-ID: 
 <CABCOCHRyQCLVX1o8fGvczj6YzFj++S_LgEt-uHpR+AmWwsa8NA@mail.gmail.com>
To: Per Andersson <per.ietf@ionio.se>
Content-Type: multipart/alternative; boundary="000000000000263e2c06533546fe"
Message-ID-Hash: MLVZX7KPUWNXI27P6QPL7O43REGIBSAJ
X-Message-ID-Hash: MLVZX7KPUWNXI27P6QPL7O43REGIBSAJ
X-MailFrom: andy@yumaworks.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: =?utf-8?q?=5Bnetconf=5D_Re=3A_yang-library-augmentedby=3A_Mix_of_deprecated/?=
 =?utf-8?q?current_in_leaf-list?=
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/netconf/Wuhltp99F8lJlcvuOeOBJL3X7kM>
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>

--000000000000263e2c06533546fe
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, May 31, 2026 at 1:21=E2=80=AFPM Per Andersson <per.ietf@ionio.se> w=
rote:

> On Fri, May 22, 2026 at 7:33=E2=80=AFAM <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 th=
em
> 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 als=
o
> aware that ncclient and NSO is using RFC 8525 NMDA yang-library.
>
> Cisco NSO and ConfD, and Ductus DMAP supports both RFC 8525 and
> RFC 7895 yang-library. It seems like sysrepo supports both as well while
> clixon only mandates RFC 8525.
>
> When I was still at Cisco NSO treated an older fleet and maturity
> grade in deployments as first class citizens. Deployment and
> adoption takes time, as you know.
>
> It seems that it isn't so easy to draw any conclusions on contemporary
> support or deployments for RFC 7895.
>
>
I am glad to learn that many toolchains support RFC 8525.
The issue is not 7985 vs 8525 but rather /modules-state vs /yang-library,
since RFC 8525 contains both subtrees.


> I propose YANG module just changed to what I suggested.
> It is a quick and effortless change and seems to be the path
> of least resistance.
>
>
>

I believe the original request to support /modules-state was from me.
Now it is not so clear this is needed or a good idea.

Since this new augment may not be known to the client,
it is better to leave /modules-state stable, and only introduce this
issue to the /yang-library subtree.

Both these subtrees can be large, so it is good to encourage vendors to use
the /yang-library subtree, so /modules-state can eventually be removed from
the server.


--
> Per
>


Andy



>

>
> >
> > 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=E2=80=AFAM <Thomas.Graf@swisscom.com> wrot=
e:
> >
> > Dear Andy,
> >
> >
> >
> > Reading 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" o=
r
> >
> >    "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 w=
e
> 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=E2=80=AFPM 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 =E2=80=9Cerrata=E2=80=9D.
> >
> >
> >
> > 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 i=
s
> 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=E2=80=AFAM, 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 to netconf-leave@ietf.org
>

--000000000000263e2c06533546fe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, May 31,=
 2026 at 1:21=E2=80=AFPM Per Andersson &lt;<a href=3D"mailto:per.ietf@ionio=
.se">per.ietf@ionio.se</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">On Fri, May 22, 2026 at 7:33=E2=80=AFAM &lt;<a href=
=3D"mailto:Thomas.Graf@swisscom.com" target=3D"_blank">Thomas.Graf@swisscom=
.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Dear Andy,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Thanks.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; AB&gt; The new /yang-library subtree is to support NMDA, which is rare=
ly used.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; To which implementation are you refering to?<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; 5 years ago I would have agreed with you. I am aware that the followin=
g network operating systems have updated their implementations a while ago:=
<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Cisco IOS XR, XE and NX-OS<br>
&gt;<br>
&gt; Juniper JunOS<br>
&gt;<br>
&gt; Nokia SR-OS<br>
&gt;<br>
&gt; Huawei VRP (OLT, IP and SDWAN)<br>
&gt;<br>
&gt; Nokia SR-OS<br>
&gt;<br>
&gt; Arista EOS<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Since usually network operating systems have a lifecycle of 1-3 years,=
 having network operating systems which still doesn&#39;t support RFC 8525 =
are rare in Swisscom&#39;s network and if there are, they are already plann=
ed to be upgraded.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I have seen network operating system implementations where the develop=
ment 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 dr=
aft-ietf-netconf-yang-library-augmentedby. All of them chose to augment yan=
g-library on RFC 8525 based implementations.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On the YANG library side which the OSS systems are using. We did a com=
prehensive feature comparison between libyang, yangtools and yangkit. From =
what we observed there is that today, only libyang out of the 3 has YANG li=
brary support. In yangkit the YANG library support is under development whe=
re in yangtools we are considering code contribution. RFC 7895 is no longer=
 considered there. From my personal experience, I am also aware that ncclie=
nt and NSO is using RFC 8525 NMDA yang-library.<br>
<br>
Cisco NSO and ConfD, and Ductus DMAP supports both RFC 8525 and<br>
RFC 7895 yang-library. It seems like sysrepo supports both as well while<br=
>
clixon only mandates RFC 8525.<br>
<br>
When I was still at Cisco NSO treated an older fleet and maturity<br>
grade in deployments as first class citizens. Deployment and<br>
adoption takes time, as you know.<br>
<br>
It seems that it isn&#39;t so easy to draw any conclusions on contemporary<=
br>
support or deployments for RFC 7895.<br>
<br></blockquote><div><br></div><div>I am glad to learn that many toolchain=
s support RFC 8525.</div><div>The issue is <span class=3D"Asgive ng" style=
=3D"border-style:none;background:none">not 7985 vs 8525 but rather /modules=
-state vs</span> /yang-library,</div><div>since RFC 8525 contains both subt=
rees.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>
<br>
I propose YANG module just changed to what I suggested.<br>
It is a quick and effortless change and seems to be the path<br>
of least resistance.<br>
<br>
<br></blockquote><div><br></div><div><br></div><div>I believe the original =
request to support /modules-state <span class=3D"Asgive ng" style=3D"border=
-style:none;background:none">was</span> from me.</div><div>Now it=C2=A0is n=
ot so clear this is needed or a good idea.</div><div><br></div><div>Since <=
span class=3D"Asgive ng" style=3D"border-style:none;background:none">this n=
ew augment may not be known to the client,</span></div><div>it is better to=
 leave /modules-state stable, and only introduce this</div><div>issue to th=
e /yang-library subtree.</div><div><br></div><div>Both these subtrees can b=
e large, so it is good to encourage vendors to <span class=3D"Asgive ng" st=
yle=3D"border-style:none;background:none">use</span></div><div>the=C2=A0/ya=
ng-library subtree, so /modules-state can eventually be removed from the se=
rver.</div><div><br></div><div><br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">
--<br>
Per<br></blockquote><div><br></div><div><br></div><div>Andy</div><div><br><=
/div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=C2=
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
&gt;<br>
&gt;<br>
&gt; Best wishes<br>
&gt;<br>
&gt; Thomas<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: Andy Bierman &lt;<a href=3D"mailto:andy@yumaworks.com" target=3D=
"_blank">andy@yumaworks.com</a>&gt;<br>
&gt; Sent: Thursday, May 21, 2026 6:43 PM<br>
&gt; To: Graf Thomas, SCS-INI-NET-VNC-E2E &lt;<a href=3D"mailto:Thomas.Graf=
@swisscom.com" target=3D"_blank">Thomas.Graf@swisscom.com</a>&gt;<br>
&gt; Cc: <a href=3D"mailto:mjethanandani@gmail.com" target=3D"_blank">mjeth=
anandani@gmail.com</a>; <a href=3D"mailto:netconf@ietf.org" target=3D"_blan=
k">netconf@ietf.org</a>; <a href=3D"mailto:draft-ietf-netconf-yang-library-=
augmentedby@ietf.org" target=3D"_blank">draft-ietf-netconf-yang-library-aug=
mentedby@ietf.org</a><br>
&gt; Subject: Re: [netconf] Re: yang-library-augmentedby: Mix of deprecated=
/current in leaf-list<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Be aware: This is an external email.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Thu, May 21, 2026 at 8:21=E2=80=AFAM &lt;<a href=3D"mailto:Thomas.G=
raf@swisscom.com" target=3D"_blank">Thomas.Graf@swisscom.com</a>&gt; wrote:=
<br>
&gt;<br>
&gt; Dear Andy,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Reading <a href=3D"https://datatracker.ietf.org/doc/html/rfc7950#secti=
on-7.21.2" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/html/rfc7950#section-7.21.2</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 o=C2=A0 &quot;deprecated&quot; indicates an obsolete defi=
nition, but it permits<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0new/continued implementation in order to fos=
ter interoperability<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0with older/existing implementations.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 If a definition is &quot;current&quot;, it MUST NOT refer=
ence a &quot;deprecated&quot; or<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 &quot;obsolete&quot; definition within the same module.<b=
r>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I believe that what RFC 7950 meant to say it that when something is de=
precated, it should not be extended anymore because it is deprecated.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Even though we can trick the compiler with a leaf-list, I don&#39;t th=
ing we are acting in the spirit of RFC 7950 and RFC 8525 authors.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Therefore I believe the best option is to remove<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0augment &quot;/yanglib:modules-state/yanglib:module&quot; =
{<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0status deprecated;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0description<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;Adds Augmented-by leaf-list to the lis=
t of modules of a module set&quot;;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0uses augmented-by;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0}<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; from ietf-yang-library-augmentedby. As an implementor who implements i=
etf-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 pu=
blished 7 years ago.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I don&#39;t care if the /modules-state augments is removed.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The new /yang-library subtree is to support NMDA, which is rarely used=
.<br>
&gt;<br>
&gt; The added complexity for the client is non-trivial.<br>
&gt;<br>
&gt; A non-NMDA server has no reason to update to RFC 8525.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Best wishes<br>
&gt;<br>
&gt; Thomas<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Andy<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: Andy Bierman &lt;<a href=3D"mailto:andy@yumaworks.com" target=3D=
"_blank">andy@yumaworks.com</a>&gt;<br>
&gt; Sent: Friday, May 15, 2026 6:09 PM<br>
&gt; To: Mahesh Jethanandani &lt;<a href=3D"mailto:mjethanandani@gmail.com"=
 target=3D"_blank">mjethanandani@gmail.com</a>&gt;<br>
&gt; Cc: NETCONF WG &lt;<a href=3D"mailto:netconf@ietf.org" target=3D"_blan=
k">netconf@ietf.org</a>&gt;; <a href=3D"mailto:draft-ietf-netconf-yang-libr=
ary-augmentedby@ietf.org" target=3D"_blank">draft-ietf-netconf-yang-library=
-augmentedby@ietf.org</a><br>
&gt; Subject: [netconf] Re: yang-library-augmentedby: Mix of deprecated/cur=
rent in leaf-list<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Be aware: This is an external email.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Thu, May 14, 2026 at 12:41=E2=80=AFPM Mahesh Jethanandani &lt;<a hr=
ef=3D"mailto:mjethanandani@gmail.com" target=3D"_blank">mjethanandani@gmail=
.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi WG,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The document is currently in the RFC Editor queue and we need to decid=
e fairly quickly what to do with this =E2=80=9Cerrata=E2=80=9D.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The suggestion from Per is small and doable with where the document is=
, if the WG agrees that the change is needed.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The change looks OK.<br>
&gt;<br>
&gt; It is unfortunate that the status-stmt has so many issues.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; This does violate a MUST NOT rule, so it should be fixed.<br>
&gt;<br>
&gt; However, the accepted meaning of &#39;deprecated&#39; is that the sche=
ma node is implemented, but<br>
&gt;<br>
&gt; it may be removed in a future module revision.=C2=A0 =C2=A0The rule ab=
out &#39;current&#39; MUST NOT reference &#39;deprecated&#39;<br>
&gt;<br>
&gt; is therefore ignored.=C2=A0 Since &#39;obsolete&#39; means the node is=
 not implemented, any reference to &#39;obsolete&#39; will cause an error.<=
br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Thanks.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Andy<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On May 13, 2026, at 8:13=E2=80=AFAM, Per Andersson &lt;<a href=3D"mail=
to:per.ietf@ionio.se" target=3D"_blank">per.ietf@ionio.se</a>&gt; wrote:<br=
>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt; The ietf-yang-library-augmentedby.yang has the following<br>
&gt; construct:<br>
&gt;<br>
&gt;=C2=A0 grouping augmented-by {<br>
&gt;=C2=A0 =C2=A0 leaf-list augmented-by {<br>
&gt;=C2=A0 =C2=A0 =C2=A0 type leafref {<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 path &quot;../../yanglib:module/yanglib:nam=
e&quot;;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 }<br>
&gt;=C2=A0 }<br>
&gt;<br>
&gt;=C2=A0 augment &quot;/yanglib:modules-state/yanglib:module&quot; {<br>
&gt;=C2=A0 =C2=A0 status deprecated;<br>
&gt;=C2=A0 =C2=A0 uses augmented-by;<br>
&gt;=C2=A0 }<br>
&gt;<br>
&gt; Trying to compile this module yields a warning because:<br>
&gt;<br>
&gt; * the &quot;module&quot; container is deprecated,<br>
&gt; * the &quot;augmented-by&quot; leaf-list is implicitly current<br>
&gt; * the leafref &quot;yanglib:name&quot; is deprecated<br>
&gt;<br>
&gt; This is not allowed per RFC 7950 Section 7.21.2:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0If a definition is &quot;current&quot;,=C2=A0 it MUST NOT =
reference a<br>
&gt;=C2=A0 =C2=A0&quot;deprecated&quot; or &quot;obsolete&quot; definition =
within the same<br>
&gt;=C2=A0 =C2=A0module.<br>
&gt;<br>
&gt; The issue is that the status statement is not inherited,<br>
&gt; see yang-next issue #27 [0].<br>
&gt;<br>
&gt;<br>
&gt; I think we should create YANG modules that follow the<br>
&gt; specifications.<br>
&gt;<br>
&gt; Suggest that the grouping is rolled out in the module,<br>
&gt; and stated explicitly in both augments:<br>
&gt;<br>
&gt;=C2=A0 augment &quot;/yanglib:yang-library/yanglib:module-set/yanglib:m=
odule&quot; {<br>
&gt;=C2=A0 =C2=A0 leaf-list augmented-by {<br>
&gt;=C2=A0 =C2=A0 =C2=A0 type leafref {<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 path &quot;../../yanglib:module/yanglib:nam=
e&quot;;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 }<br>
&gt;=C2=A0 }<br>
&gt;<br>
&gt;=C2=A0 augment &quot;/yanglib:modules-state/yanglib:module&quot; {<br>
&gt;=C2=A0 =C2=A0 status deprecated;<br>
&gt;=C2=A0 =C2=A0 leaf-list augmented-by {<br>
&gt;=C2=A0 =C2=A0 =C2=A0 status deprecated;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 type leafref {<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 path &quot;../../yanglib:module/yanglib:nam=
e&quot;;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 }<br>
&gt;=C2=A0 }<br>
&gt;<br>
&gt; Not as elegant as the module is defined now, but at least<br>
&gt; the compiler doesn&#39;t complain and we follow YANG.<br>
&gt;<br>
&gt;<br>
&gt; [0] <a href=3D"https://github.com/netmod-wg/yang-next/issues/27" rel=
=3D"noreferrer" target=3D"_blank">https://github.com/netmod-wg/yang-next/is=
sues/27</a><br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Per<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Mahesh Jethanandani<br>
&gt;<br>
&gt; <a href=3D"mailto:mjethanandani@gmail.com" target=3D"_blank">mjethanan=
dani@gmail.com</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; netconf mailing list -- <a href=3D"mailto:netconf@ietf.org" target=3D"=
_blank">netconf@ietf.org</a><br>
&gt; To unsubscribe send an email to <a href=3D"mailto:netconf-leave@ietf.o=
rg" target=3D"_blank">netconf-leave@ietf.org</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; netconf mailing list -- <a href=3D"mailto:netconf@ietf.org" target=3D"=
_blank">netconf@ietf.org</a><br>
&gt; To unsubscribe send an email to <a href=3D"mailto:netconf-leave@ietf.o=
rg" target=3D"_blank">netconf-leave@ietf.org</a><br>
</blockquote></div></div>

--000000000000263e2c06533546fe--

