RE: copy-config

["David B Harrington" <dbharrington@comcast.net>]

Hi,

This sounds to me like a detail related solely to implementation
choices. I suggest you read the whole command so you know both the
source and target, and then you can, in your implementation, process
the arguments in the order you choose. 

It would probably be a good idea to validate the whole command before
starting processing, because this could make your implementation more
robust against mal-formed requests, including deliberate attempts to
cause denial of service to other users of the system.

David Harrington
dbharrington@comcast.net

> -----Original Message-----
> From: owner-netconf@ops.ietf.org 
> [mailto:owner-netconf@ops.ietf.org] On Behalf Of Martin Bjorklund
> Sent: Friday, December 09, 2005 6:17 AM
> To: netconf@ops.ietf.org
> Subject: copy-config
> 
> Hi,
> 
> The <copy-config> operation takes source and target as parameters.
I
> think the order of these is wrong - an implementation needs to
buffer
> the entire inline config before knowing which target is used.  I
> suggest that the order is reversed - target before source.
> 
> The order is correct for edit-config.
> 
> (our implementation makes use of this for both edit-config and
> copy-config in order to find a small set of diffs to apply to the
db)
> 
> 
> 
> /martin
> 
> --
> 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/>
> 



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