Hi, all, There is a comment received during the WGLC of this draft, which is about the copy scope of "resolve-system" parameter, i.e., should the server only auto-copy the minimum to make configuration valid or the entire contents of a referenced list entry?
Like any value provided by the server that is not the schema default value needs to be copied into <running> (https://www.ietf.org/archive/id/draft-ietf-netmod-system-config-06.html#section-6), should the server also copy other system nodes that is not provided in <running> when triggered by "resolve-system" parameter? Personally I don’t think this is needed for <system>-aware clients which can always read <system> to discover system-provided values, and read <intended> to get a merged view of <system> and <running>. This is mainly the consideration for non-NMDA clients that has no way to discover system configuration and thus any data missing from <running> will result in the client having the wrong impression. On the other hand, copy-all might be easier to implement for the server than to calculate the minimum. Any thoughts? Should this be addressed in this document? Best Regards, Qiufang //co-author -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Friday, May 31, 2024 3:06 PM To: [email protected] Cc: [email protected] Subject: [netmod] I-D Action: draft-ietf-netmod-system-config-06.txt Internet-Draft draft-ietf-netmod-system-config-06.txt is now available. It is a work item of the Network Modeling (NETMOD) WG of the IETF. Title: System-defined Configuration Authors: Qiufang Ma Qin Wu Chong Feng Name: draft-ietf-netmod-system-config-06.txt Pages: 39 Dates: 2024-05-31 Abstract: This document defines how a management client and server handle YANG- modeled configuration data that is instantiated by the server itself. The system-defined configuration can be referenced (e.g., leafref) by configuration explicitly created by a client. The Network Management Datastore Architecture (NMDA) defined in RFC 8342 is updated with a read-only conventional configuration datastore called "system" to expose system-defined configuration. This document updates RFC 8342, RFC 6241, RFC 8526 and RFC 8040. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-system-config/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-netmod-system-config-06 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-netmod-system-config-06 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected] _______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
