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

[Andy Bierman <[e-mail]>]

Martin Bjorklund wrote:
> Phil Shafer <[e-mail]> wrote:
>   
>> Andy Bierman writes:
>>     
>> ....
>>     
>>>   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.)
>
>   

The IETF is moving forward with YANG and standard
NETCONF data models will use YANG.

Technically, a 4741 server can contain a string.
That does not mean we have to allow that  in 4741bis,
now that we are using YANG instead of continuing
with an ad-hoc opaque content layer.

Since the 'single-string' <config> is completely
incompatible with YANG modules, there is no role
for such a server implementation in the standard.

But we can remove the description-stmt text in question,
and be silent on this issue.  It is a market decision
whether or not a vendor wants to sell a NETCONF server
that can never implement a YANG module.


>
> /martin
>
>   

Andy