Hi Qiufang, I think there are use-cases for "immutable" even outside of system config so we may not want to restrict it to system config.
I'm not sure it would be as simple as erroring when a write is attempted to that value. Are you talking about an error at edit time, or at commit/validation time ? What if the value configured is the same as the current value ? It is probably best if this is a validation/commit time check. If the immutable leaf is inside a list entry, then it should probably be acceptable for the server to allow a change to the leaf by destroying and re-creating the list entry under the hood. i.e. allow a change to the immutable item (which is in line with configurations being "declarative" - just get me there if possible). Jason From: netmod <[email protected]> On Behalf Of maqiufang (A) Sent: Monday, November 22, 2021 7:12 AM To: [email protected] Subject: [netmod] "immutable" flag Hi, all There are some system configuration which may not be modifiable for clients(e.g., interface "name" and "type"). Should we define an "immutable" flag to indicate to the clients which system configuration is read-only or which is not? The server will return an error if the clients attempt to configure a value for a system defined data node with an "immutable" flag. My assumption is that this annotation should be carried only when the clients retrieve <running> with "with-system" parameter to get a merged view. Suggestions, comments and concerns about this issue? Best Regards, Qiufang Ma
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
