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

[Mark Ellison <ellison at ieee.org>]

On Fri, Oct 2, 2009 at 7:08 AM, Martin Bjorklund <mbj at tail-f.com> wrote:
> Mark Ellison <ellison at ieee.org> wrote:
>> On Thu, Oct 1, 2009 at 5:45 PM, Martin Bjorklund <mbj at tail-f.com> wrote:
>> > Mark Ellison <ellison at ieee.org> wrote:

[deletions]

>> > 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).
>>
>> Okay- duly noted.  However, it would seem that a <copy-config> from a
>> remote http/file to a local file would serve a use case where there is
>> one of many of the same model devices where a configuration is
>> validated and this configuration is then moved out to the many
>> devices- which will then load the config from the local url/file at
>> some future (possibly coordinated) time.
>>
>> I don't think the protocol precludes this.
>
> If not, what checks, if any, should be done by copy-config when both
> target and source are urls?  Is this legal:
>
>    <copy-config>
>      <target>
>        <url>file://incoming.conf</url>
>      </target>
>      <source>
>        <url>http://www.ietf.org/index.html</url>
>      </source>
>    </copy-config>
>
>

I see your point that <copy-config> could be misused by placing
garbage into a local file.  However, the same could be attempted when
the target is a configuration data store which is then saved to a
local file.

When a client is using <copy-config> properly, it seems an extra step
to load a remote source into a configuration date store in order to
copy to a local file and an extra step to load a local file into a
configuration data store in order to save to a remote file.


[deletions]

>
>
> /martin
>

Regards,

Mark