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

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

Mark Ellison <ellison at ieee.org> wrote:
> Regarding use of URL in the <edit-config> protocol operation:
> 
> sxn 7.2., "<edit-config>" - states "...such as using a local file, a
> remote file, or inline."
> 
> Within section 8.8. "URL capability", section 8.8.5.1 "<edit-config>"
> states, "If the <url> element is specified, then it should identify a
> local configuration file."
> 
> My best guess at interpreting the intent would be that 8.8.5.1
> suggests that a URL *target* in an  <edit-config> operation should be
> a file that is local to the NETCONF server.  And, I assume that a URL
> *source* in an <edit-config> operation may be a file that is local or
> remote to the NETCONF server.

I think 8.8.5.1 is pretty clear.  It says:

   The :url capability modifies the <edit-config> operation to accept
   the <url> element as an alternative to the <config> parameter.  If
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   the <url> element is specified, then it should identify a local
   configuration file.

I.e. the *source* url should be a local file.  According to 8.8.5.1,
using url as a *target* is not supported at all.

7.2. also does not allow a url as target, but it does say:

      This operation allows the new configuration to be expressed in
                                ^^^^^^^^^^^^^^^^^
      several ways, such as using a local file, a remote file, or
      inline.

So the word "remote file" in 7.2 contradicts the text in 8.8.5.1, and
it also contradicts the next paragraph in 7.2.

However, it is not clear to me why the edit-config source url should
be a local file.  The copy-config operation does not have such a
restriction.

I don't think edit-config of a *target* url was ever intended to be
supported.


/martin