Re: [Netconf] <edit-config> and remote URLs

[Martin Bjorklund <mbj at tail-f.com>]

Mark Ellison <ellison at ieee.org> wrote:
> So the "target" of <edit-config> can only be one of running, candidate
> or startup configuration datastore as allowed by the NETCONF server
> capabilities?

In fact, it can not be <startup>.  See 8.7.5.1.  I recommend that you
look at the YANG model in draft-ietf-netconf-4741bis-01 - it is a bit
more precise than the old XSD.

> And, it looks like there is a multi-step process involving
> <copy-config> and <edit-config>.  I can use a remote url as source and
> a local url as target in the <copy-config> operation to move
> configuration data onto the local server, then (lock and) use a local
> source url with the <edit-config> to update the candidate target, then
> validate, etc.  Finally, I can use <copy-config> to move the 'new
> configuration' contained in the candidate datastore to either a local
> or a remote url/file.

This is a use case described in Appendix D.  But I am not sure if
copy-config was intended to be a "ftp" operation, i.e. copy any file?

I think copy-config makes sense only when at least one of target and
source is a data store.  (Then it is like a load / save backup
operation).


/martin