Re: Separation of configuration and control - good or bad?

[Phil Shafer <phil@juniper.net>]

Larry Menten writes:
>The Enns model is one in which
>configuration is expressed as the transformation of a document.  This is why
>you must lock the document before you operate on it.

Regardless of the configuration change you are making, locking the
device seems like a requirement. This seems independent of your
view of configuration-as-tree .vs. configuration-as-hierarchy
.vs. configuration-as-set-of-strings. If you can't lock it,
you can't prevent other sources of configuration (applications or
users) from turning your change from benign to dangerous.

Thanks,
 Phil

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>