[netconf] Jan & Nacio's Comments: draft-lincla-netconf-yang-library-augmentation

Zhuoyao LIN <zephyre888@gmail.com> Mon, 04 March 2024 17:55 UTC

Return-Path: <zephyre888@gmail.com>
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 7A780C14F61C for <netconf@ietfa.amsl.com>; Mon, 4 Mar 2024 09:55:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.854
X-Spam-Level:
X-Spam-Status: No, score=-6.854 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2FEIW_kkVJxL for <netconf@ietfa.amsl.com>; Mon, 4 Mar 2024 09:55:01 -0800 (PST)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5E3AC14F680 for <netconf@ietf.org>; Mon, 4 Mar 2024 09:55:01 -0800 (PST)
Received: by mail-qv1-xf2d.google.com with SMTP id 6a1803df08f44-68f51ba7043so32635696d6.3 for <netconf@ietf.org>; Mon, 04 Mar 2024 09:55:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709574901; x=1710179701; 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=clBcE5wkMhxN8HnRXP390yc5+s3pOdAZhHRntdsvDFo=; b=etxS0zxCy0RKXnfktmY5CwK9OlA0Gyg1eTKkvLftzMRLfuKr2CvaLXmEI5xhCn1jve j8uxpB/6P8XDUUWVr22PmZCgz2e2oKPxE8/2xyOyZCb04ScM4wbSZDg4UO+aPee2shz2 Pr4AT0WlqzTbOuBfgGcGpHOdVRGWIPNsvW9YYQ60BNuoaU25IWj9z/O/l0nUwKzlS0T6 o3bO52rs8DkPz9OpQ1YI3/0dRjV3xchl+PtBe93URFO6v/hWk1/2to2u2FzT9uGIROQH qPzOZMNoqxdaLpWVDbRFwKfSp1QgoApBVzkZ6Gu4JhhBzdu99WDSYYzcTrUlqlK9gUKy 5B7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709574901; x=1710179701; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=clBcE5wkMhxN8HnRXP390yc5+s3pOdAZhHRntdsvDFo=; b=honSHyoL99svvXiCqTUszRG6ajALmTZcB151HmE2aucZtU6gMaQl8+ZAKFw7KdGAWl 9y0PZNoOdx4PjctIoZo7+0fV+IOY5Vv5aSG4xu+/PxdhSveuP5eNPlHlPsaK6ZDmBQ7b 9ZtqO75paOv6k3NRUlwADeBGScHIpw5TdRLICsjjwa6mkgV8I/azbtry7dgfSoNKpmbG Iyd/pSpYFcgT7dM7GGQXg60bdNlFtOzouwDp4IvFrYHX7YXtBJ2alxHs0j5M/FI6BTsU SGHaw1+JW2HvVwW5Lq85sy4N4NEr24qdG18NUlN6FpxbghE7QJddxJDZTnxr5dmf11et Wkaw==
X-Gm-Message-State: AOJu0YwW9hhaK+Icc+UcyXOMdTYYrJlN3oQ+AsZEnXN9hRWSxVAs0ukh pyTJKdjehs9qemjLz98YESH5PTtUe3WWbflHVNRrjAuuRj1fr3UpVEWNfgPX3suPCw4Yt3v2nOh N/dNLQLHwk7tlRsulhOZgjmJVikrZTa+W1CacBlmFX/Y=
X-Google-Smtp-Source: AGHT+IFZXDhgKs43mvOiYo/0o6zGNFGguTK4NLBxZ8C/6t7mmRa4l+YABOEHGoJuOzajxhT1RRgVgk+SpaUoxkgQKow=
X-Received: by 2002:a0c:e4ce:0:b0:68f:730f:7595 with SMTP id g14-20020a0ce4ce000000b0068f730f7595mr9540684qvm.37.1709574900691; Mon, 04 Mar 2024 09:55:00 -0800 (PST)
MIME-Version: 1.0
References: <169926957480.41732.13691497170003209371@ietfa.amsl.com> <abb8d6c9-71d5-75b2-9988-b1b04ba158a3@huawei.com> <8EB468CE-61A5-49BA-8E2A-D647804A4E97@cisco.com> <b5d4f252-7814-fe8b-b492-f967e718920d@huawei.com>
In-Reply-To: <b5d4f252-7814-fe8b-b492-f967e718920d@huawei.com>
From: Zhuoyao LIN <zephyre888@gmail.com>
Date: Mon, 04 Mar 2024 17:54:50 +0000
Message-ID: <CADF4xzUgXcBLzX1oLvFLWXRgD3K4VbnZbOyiu3jitu-1cLCKYQ@mail.gmail.com>
To: netconf@ietf.org
Cc: "Jan Lindblad (jlindbla)" <jlindbla=40cisco.com@dmarc.ietf.org>, me <benoit.claise@huawei.com>, ignacio.dominguezmartinez@telefonica.com
Content-Type: multipart/alternative; boundary="000000000000ac38f00612d96c5c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/cAHLQP6-N3rIUIXLYbGqR7TnLnw>
Subject: [netconf] Jan & Nacio's Comments: draft-lincla-netconf-yang-library-augmentation
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 04 Mar 2024 17:55:02 -0000

Dear all,

Following the comments we have for the last version of
draft-lincla-netconf-yang-library-augmentation, I have made changes in the
new version:
https://datatracker.ietf.org/doc/draft-lincla-netconf-yang-library-augmentation/

Summary:

1) The leaf-ref path has been updated according to Jan and Nacio's
suggestions, see
https://datatracker.ietf.org/doc/draft-lincla-netconf-yang-library-augmentation/#:~:text=leaf%2Dlist%20augmented%2Dby%20%7B%0A%20%20%20%20%20%20%20%20%20type%20leafref%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20path%20%22../../yanglib%3Amodule/yanglib%3Aname%22%3B%0A%20%20%20%20%20%20%20%20%20%7D

The explanation of that, the augment modules defined in another module set
is out of scope, is not mentioned in the current version, but I will put it
in the future version.


Yanglint validation example is provided in the appendix A:
 https://datatracker.ietf.org/doc/draft-lincla-netconf-yang-library-augmentation/#:~:text=org/info/rfc8641%3E.-,Appendix%20A.%20%20YANG%20module%20validation%20with%20yanglint,-This%20section%20gives
<https://datatracker.ietf.org/doc/draft-lincla-netconf-yang-library-augmentation/#:~:text=org/info/rfc8641%3E.-,Appendix%20A.%20%20YANG%20module%20validation%20with%20yanglint,-This%20section%20gives>


2) Nacio's use case has been merged in Section 3.


Regards,
Zhuoyao Lin


On Mon, 13 Nov 2023 at 17:07, Benoit Claise <benoit.claise@huawei.com>
wrote:

> Hi Jan,
>
> Thanks for your review and comment.
> See inline.
>
> On 11/9/2023 6:17 PM, Jan Lindblad (jlindbla) wrote:
>
> 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.
>
> I like the "augmented-by" proposal.
> And good advice on the two leafref keys, which we will implement.
>
> Regards, Benoit
>
>
> Best Regards,
> /jan
>
>
> On 6 Nov 2023, at 23:02, Benoit Claise
> <benoit.claise=40huawei.com@dmarc.ietf.org>
> <benoit.claise=40huawei.com@dmarc.ietf.org> 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
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>
>
>
>