From nobody Mon Jan 24 05:49:20 2022
Return-Path: <mvasko@cesnet.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 1C31A3A07A7
 for <netmod@ietfa.amsl.com>; Mon, 24 Jan 2022 05:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
 header.d=cesnet.cz
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 3OzlHSdvdo1w for <netmod@ietfa.amsl.com>;
 Mon, 24 Jan 2022 05:49:15 -0800 (PST)
Received: from kalendar.cesnet.cz (kalendar.cesnet.cz [78.128.211.34])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id D2BCD3A07A5
 for <netmod@ietf.org>; Mon, 24 Jan 2022 05:49:14 -0800 (PST)
Received: by kalendar.cesnet.cz (Postfix, from userid 110)
 id 1931660068; Mon, 24 Jan 2022 14:49:10 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz;
 s=kalendar; t=1643032150;
 bh=y/97Qbpk4Qp6XkR/WgIan6ioHOYITNuoFp8euR9x0NI=;
 h=From:In-Reply-To:Date:To:Subject;
 b=kPmBKpVwYu89DrMhd5v2f2qLUBdeyEUngfR3Ovt05PFGECKez4ITKjtyN282Lk9FA
 HK+CIwaQMkCsXfbgRTAtc4gtgwNjHhFiTelONoV9Jj4yqSSXen4V1fXLWYeML0cQf2
 ymlSHZI214QVVGFHQ+ifP58ngFOAXjAfwyJxp17k=
From: =?utf-8?q?Michal_Va=C5=A1ko?= <mvasko@cesnet.cz>
In-Reply-To: <19e7-61eea580-31-3a495240@76250820>
Content-Type: text/plain; charset="utf-8"
X-Forward: 84.42.188.124
Date: Mon, 24 Jan 2022 14:49:10 +0100
To: "netmod" <netmod@ietf.org>
MIME-Version: 1.0
Message-ID: <19e5-61eeae80-23-1f5ff2c0@262915203>
User-Agent: SOGoMail 5.5.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/JYMH1614C_4dLb38Fhz9YgdlAZg>
Subject: Re: [netmod] =?utf-8?q?Schema_Mount?=
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>,
 <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>,
 <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 13:49:19 -0000

Sorry, adding links. 

> Hello,
> I wanted to implement this RFC [1] but I have great difficulty unders=
tanding how exactly it should work so I would like to ask for some clar=
ification.
> 
> As for the ietf-yang-library data, they are mentioned several times b=
ut I could find no details as to how exactly they should look like. The=
re is an example [2], which has only 'ietf-yang-library:modules-state' =
data tree that is deprecated. Am I to understand that is what is expect=
ed?
> 
> Another thing, there are 3 ways mentioned [3] as to when to specify t=
he schema (YANG modules) for the mounted data and that only 2nd and 3rd=
 are covered in the RFC. However, I was not able to find anything more =
about the 2nd option (implementation-time) and think that everything co=
ncerns only the 3rd option (run-time).
> 
> Lastly, I was also looking at another RFC [4] and its examples. There=
 I could see 'ietf-yang-library:yang-library' data tree instead meaning=
 every 'module-set' and corresponding 'schema' need to be referenced by=
 some 'datastore'. The consequence would be that one must know the data=
store of the data before they can be parsed, is that right? Moreover, f=
or parsing one would also need the 'ietf-yang-schema-mount:schema-mount=
s' data (which are found in the operation data in the example) but wher=
e should the NETCONF/RESTCONF server (for instance) get them?
> 
> Thanks for any clarification.
> 
> Regards,
> Michal

[1] https://datatracker.ietf.org/doc/html/rfc8528
[2] https://datatracker.ietf.org/doc/html/rfc8528#appendix-A.2
[3] https://datatracker.ietf.org/doc/html/rfc8528#page-5
[4] https://datatracker.ietf.org/doc/html/rfc8529#appendix-A.3

> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=

> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

