Re: [yang-doctors] Deprecated Nodes

[Juergen Schoenwaelder <[e-mail]>]

I fear the answer to this seemingly simple question is not that
simple. The reason is that NETCONF supports different implementation
styles, RFC 6243 gives you an idea what can all happen if we just look
at defaults.

Personally, I consider only the 'explicit' basic mode reasonable: I
want the system to remember what I configure and I expect that the
server does not do automatic conversions on the fly unless I have
explicitely requested this. I want the server to return what I
configured without changes (ignoring canonicalization of value
representations).

Systems that implement other modes often do not recall what was
actually configured but instead they generate what might have been
configured from the current state of the system. On such a system, if
you have multiple leafs for the same object, say one current and the
other deprecated, it might return values for both leafs or only the
value for the current leaf. I do not think this is really regulated.
But systems not implementing 'explicit' basic mode are surprising in
general from a clients perspective, people who have to deal with them
may be used to surprising behavior.

/js

On Thu, Aug 08, 2019 at 02:44:02PM +0000, Acee Lindem (acee) wrote:
> When a client retrieves configuration for a device, should the deprecated nodes be included in the response? For example, using NETCONF get-config? I have my own interpretation of the answer but don’t want to bias the response from others.
> 
> Thanks,
> Acee

> _______________________________________________
> yang-doctors mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/yang-doctors


-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>