Re: [netconf] New draft: Augmentiton Addition into the IETF-YANG-Library

[IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA <[e-mail]>]

Hi Jan, all,

I think this extension of YANG Library will be very helpful. The current version of YANG Library does not provide the information required by an application to discover all the dependencies that compose a YANG data model.

Let’s think of a very simple use case where an application wants to manage the interfaces of a device. Based on the current YANG Library, the application will see that there is an “ietf-interfaces” module and another “ietf-ip” module that augments the former, however, this dependency information is missing. Currently, the application needs to additionally parse these YANG modules to identify the augmentation dependency. We could include this simple use case to better illustrate the need for the extension.

My understanding of this draft is to extend YANG Library to include “augmentations” following the same approach as done for “deviations”.

I agree with Jan in renaming the dependency to “augmented-by”, which conveys more precise semantics.

Additionally, if it makes sense (YANG-wise), I would propose changing the leafref to “path "../../module/name".

Many thanks!

Best regards,
Nacho.

From: netconf <[e-mail]> on behalf of Jan Lindblad (jlindbla) <jlindbla=[e-mail]>
Date: Thursday, 9 November 2023 at 18:17
To: Benoit Claise <benoit.claise=[e-mail]>
Cc: [e-mail] <[e-mail]>, Zhuoyao LIN <[e-mail]>
Subject: Re: [netconf] New draft: Augmentiton Addition into the IETF-YANG-Library
Benoît, WG,

I listened to the presentation in the NETCONF WG, and now I have also read this draft. I think it's ok, even if it does not really provide clients with any new information that they can't access today. Since it is optional for servers to implement, I don't think there are any problems standardizing a module like this. Servers that often participate in use cases where clients find this shortcut to information useful may well choose to implement the augmentation.

If I may be very technical for a moment, I might add that the current definition of the augmentation leaf-list is a bit odd. It is a leafref referring to /yanglib:yang-library/yanglib:module-set/yanglib:module/yanglib:name. In this path there are two keys (module-set/name and module-set/module/name). That means you need two leafrefs to uniquely identify the module, one for each key leaf in the path. Instad of using a leaf-list of leafrefs here, I'd suggest modeling this as a traditional list with two leafref keys to avoid the problem. Other solutions are also possible. Perhaps naming this addition "augmented-by" would also make the contents clearer.

Best Regards,
/jan



On 6 Nov 2023, at 23:02, Benoit Claise <benoit.claise=[e-mail]> wrote:

Dear all,

Let me introduce this draft
This document augments the ietf-yang-library in [RFC8525] to provide
the augmentation list. It facilitates the process of obtaining the
entire dependencies of YANG model, by directly querying the server
YANG module.
Feedback on this brand new draft (done during the hackathon) is welcome;

Regards, Zhuoyao & Benoit

-------- Forwarded Message --------

A new version of Internet-Draft
draft-lincla-netconf-yang-library-augmentation-00.txt has been successfully
submitted by Benoit Claise and posted to the
IETF repository.

Name: draft-lincla-netconf-yang-library-augmentation
Revision: 00
Title: Augmentaiton Addition into the IETF-YANG-Library
Date: 2023-11-03
Group: Individual Submission
Pages: 13
URL: https://www.ietf.org/archive/id/draft-lincla-netconf-yang-library-augmentation-00.txt
Status: https://datatracker.ietf.org/doc/draft-lincla-netconf-yang-library-augmentation/
HTMLized: https://datatracker.ietf.org/doc/html/draft-lincla-netconf-yang-library-augmentation


Abstract:

This document augments the ietf-yang-library in [RFC8525] to provide
the augmentation list. It facilitates the process of obtaining the
entire dependencies of YANG model, by directly querying the server
YANG module.

Discussion Venues

This note is to be removed before publishing as an RFC.

Source for this draft and an issue tracker can be found at
https://github.com/Zephyre777/draft-lincla-netconf-yang-library-
augmentation.



The IETF Secretariat


_______________________________________________
netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf


________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
________________________________

Le informamos de que el responsable del tratamiento de sus datos es la entidad del Grupo Telefónica vinculada al remitente, con la finalidad de mantener el contacto profesional y gestionar la relación establecida con el destinatario o con la entidad a la que está vinculado. Puede contactar con el responsable del tratamiento y ejercitar sus derechos escribiendo a [e-mail]<mailto:[e-mail]>. Puede consultar información adicional sobre el tratamiento de sus datos en nuestra Política de Privacidad<https://www.telefonica.com/es/telefonica-politica-de-privacidad-de-terceros/>.

We inform you that the data controller is the Telefónica Group entity linked to the sender, for the purpose of maintaining professional contact and managing the relationship established with the recipient or with the entity to which it is linked. You may contact the data controller and exercise your rights by writing to [e-mail]<mailto:[e-mail]>. You may consult additional information on the processing of your data in our Privacy Policy<https://www.telefonica.com/en/wp-content/uploads/sites/5/2022/12/Telefonica-Third-data-subjects-Privacy-Policy.pdf>.

Informamos que o responsável pelo tratamento dos seus dados é a entidade do Grupo Telefónica vinculada ao remetente, a fim de manter o contato professional e administrar a relação estabelecida com o destinatário ou com a entidade à qual esteja vinculado. Você pode entrar em contato com o responsável do tratamento de dados e exercer os seus direitos escrevendo a [e-mail]<mailto:[e-mail]>. Você pode consultar informação adicional sobre o tratamento do seus dados na nossa Política de Privacidade<https://www.telefonica.com/es/politica-de-privacidade-de-terceiros/>.