I think this does not work:
[...] For <copy-config> operation,it can be used to copy
the factory default content to another datastore, however the
content of the datastore is not propagated automatically to any
other datastores.
You can't change the way things work. If something is committed to
lets say <running>, then this triggers the propagation to <intended>
and eventually <operational>. You can't come along and say that
copy-config from a particular source stops this.
Is it really useful to expose factory default to copy config? Or said
differenlty, would it not make sense to fix copy-config (at some other
place) so that it can generically work with new datastores?
The content of the factory-default datastore is usually not security
sensitive as it is the same on any device of a certain type.
I am not sure this is true.
For non-trivial devices, the default is likely not static but
something that takes into account device features available and the
specific hardware configuration present. It is actually somewhat
unclear what the factory-default datastore contains; the stuff I can
expect to see in <running> after the reset or some static stuff that
may be tweaked during the boot process to yield the initial <running>.
Or are we pretending these two are always the same?
The copyright year needs adjustment. Indentation of the YANG
statements should be fixed.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
