Subject: [Netconf] copy-config and access control

From: Andy Bierman <[email-masked]>
Date: Thu, 30 Jul 2009 10:44:58 -0700

Hi,

The <copy-config> operation is not all-or-nothing, right?

That is, if I copy some inline config into candidate, running,
or startup, what if the 10th existing node I delete causes
an access-denied error? (as I am replacing existing config
with my inline config)

Sec. 7.3 is not entirely clear on this point.
Is the agent required to do a complete validation,
or is it allowed to do stop-on-error instead?

This is one reason I do not like copy-config.
The database architecture would be much cleaner
without these imprecise overlapping operations.

(Same issue applies to delete-config in sec. 7.4)

Andy