From: Robert Wilton [mailto:rwilton@xxxxxxxxx] Sent: Thursday, July 20, 2017 3:03 AM To: Marek Hajduczenia <mxhajduczenia@xxxxxxxxx>; STDS-802-3-YANG@xxxxxxxxxxxxxxxxx Subject: Re: [802.3_YANG] Changes to 802.3 modules in light of IETF actions
Hi Marek,
On 20/07/2017 02:06, Marek Hajduczenia wrote:
Are there any other (equally dramatic) changes planned for YANG itself? That is a major overhaul to the module structures and likely place for pitfalls
No. No other significant changes like this are on the radar.
Unfortunately standards bodies move very slowly, and getting them to change direction takes a long time.
I appreciate that this change is slightly painful, but I think that it will greatly help the long term longevity of YANG and the YANG ecosystem.
Yes, you should conform to the nmda guidelines that you cite below to collapse all config-state leafs into a single container and deprecate or remove all state containers.
It is my understanding that IETF recently took a decision to change how NETCONF/RESTCONF handles datastores for YANG models. New models no longer separate configuration and state trees and existing models should deprecate state trees and move their contents to a combined configuration/state tree (see links copied below)
Do we need to make any modifications to our modules in light of the recent actions of IETF to combine configuration and state trees?