Re: [Netconf] 答复: How to specify a namespace in a options/get/head/delete request

Use cases where support for multiple versions of hardware, software, services, ... are required are quite common, in my experience. The good news is that this is well within reach for NETCONF+YANG without any sort of extensions or tweaking. What you seem to forget is that the version of the YANG model description of an object is quite separate from the version of the object that it describes. 

It's trivial to make a YANG model has a list of line cards with a choice of linecard-xyz-v13 and linecard-xyz-v14. And in the next version of the YANG model, extend the model to also include linecard-xyz-v12.

/jan

> On 7/28/2017 9:37 AM, Juergen Schoenwaelder wrote:
> ...
>> Lets not turn a simple statement into a complex nightmare. RFC 7950
>> said: A server MUST NOT implement more than one revision of a module.
>> What is the reason to relax this simple and clear statement? Just
>> because we can is not a good reason.
> 
> Back in the 1980's I encountered systems (both telco and internet) that
> could be simultaneously populated with multiple versions of a given kind
> of card, and in some cases the management properties of these versions
> differed, though usually in ways easily handled through inheritance in
> OO models.  But support for such configurations has long been considered
> beyond the scope of netconf - if one needed to do it, then rather than
> "revising" the module one would create a new one which would bear a
> remarkable resemblance to the old one, and presumably fork any module-
> specific management software accordingly.
> 
> Randy
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
> 