Re: [core] The CORE WG has placed draft-veillette-core-yang-library in state "Call For Adoption By WG Issued"

Hi Andy

I effectively see some values in supporting the module names.
However, these names should be optional leaves and not mandatory keys.
Simply augmenting the existing “ietf-yang-library” will increase its size, which makes this solution even less friendly to constrained devices and networks.

Hope to see you in MTL to discuss these changes,
Michel

From: Andy Bierman <andy@yumaworks.com>
Sent: 12 juillet 2019 17:16
To: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Cc: draft-veillette-core-yang-library@ietf.org; core-chairs@ietf.org; Core <core@ietf.org>
Subject: Re: [core] The CORE WG has placed draft-veillette-core-yang-library in state "Call For Adoption By WG Issued"

On Thu, Jul 11, 2019 at 8:32 AM IETF Secretariat <ietf-secretariat-reply@ietf.org<mailto:ietf-secretariat-reply@ietf.org>> wrote:

The CORE WG has placed draft-veillette-core-yang-library in state
Call For Adoption By WG Issued (entered by Carsten Bormann)

The document is available at
https://datatracker.ietf.org/doc/draft-veillette-core-yang-library/<https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-veillette-core-yang-library%2F&data=02%7C01%7C%7C8bb9a04c432b4f951aa308d7070e41df%7C4f6fbd130dfb415085c3d43260c04309%7C0%7C0%7C636985630142011420&sdata=y3mqrhz4doIEmRBNsvjDgs9zMMd%2FuaRcNQNNLsWQ2pE%3D&reserved=0>

I do not know if there is a clear problem statement presented and agreed upon by the CORE WG yet.
The YANG Library (RFC 8525) is used by a server to provide a client with details about the YANG modules
that are implemented in the server.

The draft proposed for adoption is a cut-and-paste-and-replace version of this RFC.
The strings used as list keys (e.g., /yang-library/module/name) are replaced by SID values.
Other key leafs such as /yang-library/schema/name are replaced by int8 leafs instead of strings.

IMO there are better solution approaches, considering that this data structure will be
relatively static, and there is a caching mechanism built into RFC 8525 to reduce
retrieval of the entire YANG library.

It does not seem realistic that a server would have only SIDs installed and no way to get the module names.
This is a short list, unlike the list of YANG data nodes. So it should be OK to simply augment the existing module
with SID values.  If the list key replacements are really needed, then a deviation module could be used by CORECONF
(e.g. deviate replace {type-stmt}) instead of a replacement module.

I agree it will be important for a CORECONF client to determine the YANG library details for each server.
This could be offline data or directly retrievable from the server. The solution need to be resolved by the WG.
I support the problem statement by not this solution.

Andy

Comment:
Till 2019-07-18

_______________________________________________
core mailing list
core@ietf.org<mailto:core@ietf.org>
https://www.ietf.org/mailman/listinfo/core<https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fcore&data=02%7C01%7C%7C8bb9a04c432b4f951aa308d7070e41df%7C4f6fbd130dfb415085c3d43260c04309%7C0%7C0%7C636985630142011420&sdata=wgigCDGdCpHKFejaAVbJ96Kqrw1ohGqKYMDlMBS2xZs%3D&reserved=0>