On Mon, Apr 24, 2023 at 08:50:02AM +0000, maqiufang (A) wrote: > > 2) The "immutable" YANG extension statement (not the metadata annotation) > designates, at the schema-level, config=true nodes that, when present in > <running/startup/candidate>, are system-defined and hence immutable. > Note that NMDA does allow clients to create an interface entry with an > interface-type value which is not yet physically present. Only when the > interface physically appears, the type cannot be modified with another value > not matching the real value the device is actually in use. >
My assumption so far is that an interface configuration is matched against hardware and it is applied if there is matching hardware. In other words, if an edit makes the interface configuration not match the hardware anymore, then the config is simply not applied anymore and the interface is left unconfigured. (The same would happen if you replace an interface with another that does not match the current config.) The idea that an interface configuration becomes partly immutable once it is applied to a matching physical interface is not really reflecting how I understand the design of N/Y. Also the notion of immutable data in candidate, which is rather a scratchpad to assemble bigger changes, seems odd to me. /js -- Jürgen Schönwälder Constructor University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://constructor.university/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
