Re: [Netconf] draft-cole-netconf-robust-config-01

[Phil Shafer <phil at juniper.net>]

Martin Bjorklund writes:
>Why don't you
>simply add a new operation <start-test> that can be used to trigger
>the tests at the server when the conrimed commit is active?

Another thing to consider that the nature of the test are typically
interwoven with the architecture of the network and the characteristics
of the change.  What test do you perform when you:

(a) change a BGP export filter
(b) change an AS number
(c) add a BGPVPN site

(a) would only affect your peer(s), (b) could have serious impact (but
that's what you wanted), and (c) should have no impact on existing
peers/sites/etc.

So given that the application is making the change, and that testing
the change is integrated with both the change and the customer
network architecture, why not use the existing "commit confirmed"
mechanism and have the application drive the testing of changes
using remote RPCs to get information off the box re: the impact
of the change?  This seems much more straight forward and was
what we had in mind from the start.

Thanks,
 Phil