[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: interesting application problems
>>>>> On Wed, 24 Nov 2004 10:17:09 -0800, "Rob Enns" <rpe@juniper.net> said:
Rob> The <commit> operation must execute atomically. If the
Rob> device is unable to commit all of the changes in the candidate
Rob> configuration datastore, then the running configuration must
Rob> remain unchanged.
Ok. Sounds good. From an implementation point of view, that may be
difficult to achieve some times. Are you going to make that a MUST?
In short, you can upload a bad configuration today that causes boxes
to fail to come up. netconf will provide them with the same power to
shoot themselves and I'm not sure you can actually achieve the above
paragraph in real life all the time.
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
--
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/>