Re: action RPC I-D

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "Andy Bierman" <ietf@andybierman.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: "'Netconf (E-mail)'" <netconf@ops.ietf.org>
> Sent: Wednesday, November 01, 2006 1:53 PM
> Subject: Re: action RPC I-D
...
> Seems like the quality of the RPC or data model definition
> and documentation would determine how predictable the result
> would be on any given system.  No different than SNMP here.
> A bad MIB design does not prove that SNMP is broken either.
...

We're not talking about SNMP.  Were talking netconf, a protocol that
was supposed to better support configuration management than SNMP.

With this kind of behaviour, what's the point of tracking configurations?
It seems the only workable solution if equipment can be this arbitrary
will be to tweak things until the device works, and then do a get-config
to figure out what the configuration really is, and hope that none of
the RPCs did things that won't be reflected in the results of get-config,
and hope that replaying the results of the get-config back into a device at
some time in the future will result in the desired configuration.

This seems somewhat suboptimal.

Randy


--
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/>