Hi -
From: "Andy Bierman" <ietf@andybierman.com>
To: "Vincent Cridlig" <vincent.cridlig@loria.fr>
Cc: "'Netconf (E-mail)'" <netconf@ops.ietf.org>
Sent: Monday, October 30, 2006 8:00 AM
Subject: Re: action RPC I-D
...
Any RPC method is potentially capable of touching any
configuration datastore in unknown ways. Rather than
define a hard-wired ACM for 7 known RPC methods, I prefer
to have a more generalized system that handles any RPC and any data.
...
From this I gather that the only way to represent the configuration
(for purposes of disaster recovery, for example) of a system that
supports these RPCs would be to record the sequence of RPCs
over the lifetime of the box so they can be replayed into the new
system. The alternative would be to retrieve the entire configuration
of the managed system as some kind of checkpoint to minimuize the
number RPC replays required. Neither approach sounds to me
like a very good way to do real configuration management.
But then, maybe I'm missing something about what edit-config
and its friends really do...