Re: [Netconf] 4741bis -- :url capability issues

[Martin Bjorklund <[e-mail]>]

Phil Shafer <[e-mail]> wrote:
> Andy Bierman writes:
> >Hi,
> >
> >Here are more issues for 4741bis:
> >
> >1) :url as a source for <edit-config>
> >   (Martin already raised this issue)
> >
> >         choice edit-content {
> >           mandatory true;
> >           anyxml config {
> >             description
> >               "Inline Config content: 'config' element.
> >                This is not full 'anyxml' because the <config>
> >                element cannot directly contain a text node.";
> >           }
> 
> I may be missing something, but why can't I put text in <config>?
> If my data model (which NETCONF doesn't care about) is text-based
> config, can I not put that config directly in the <config> element?
> 
> >           leaf url {
> >             if-feature url;
> >             type inet:uri;
> >           }
> >         }
> >
> >   The edit-config operation allows <url> as a source,
> >   but there is no explanation what the file has to contain.
> 
> The file contains data acceptable to the data model(s) supported
> by the device.  You can say "go load that file" instead of putting
> it inline with the <config> element.
> 
> >   Does it even have to be XML?
> 
> If should be any content that would be acceptable in a <config>
> element.

The problem with this that in the <config> element, you may have
several child elements, e.g.:

  <config>
    <interface xmlns="urn:ietf...:inteface">
      ...
    <interface>
    <nacm xmlns="urn:ietf....nacm">
      ...
    </nacm>
  </config>

If you just copy the stuff in the <config> element and put it into a
file, you will get an invalid XML document.  Now, this may not be a
problem, but if this is something we want to support in an
interoperable way, we need to define how this should work.

(But I don't think this is an important feature, and would rather see
it removed.)



/martin