Hi Qiufang, > > OLD: When a leaf node instance is immutable, it cannot be configured with a > different value in read-write configuration datastores (e.g. <candidate>, > <running>). It can be deleted in read-write configuration datastores (see > section 7). > NEW: When a leaf node instance is immutable, it cannot be configured with a > different value in read-write configuration datastores (e.g. <candidate>, > <running>). Though it can be created/deleted in read-write configuration > datastores. (see section 7).
This is better. Thanks. Regarding "cannot be configured". Does the draft actually state that trying to configure a different value is expected to fail? I see in the Abstract and the YANG module's "description" the following text: Clients may use "immutable" annotations provided by the server, to know beforehand why certain otherwise valid configuration requests will cause the server to return an error. This certainly hints at the expected server behavior, but doesn't seem to require it. Should it be stated somewhere that servers MUST return an error if a client attempts the violate immutability for a node the server has stated/annotated to be immutable? Kent // contributor
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
