Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802.3_YANG] Changes to 802.3 modules in light of IETF actions

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




From: Mahesh Jethanandani [mailto:mjethanandani@xxxxxxxxx]
Sent: Wednesday, July 19, 2017 2:14 PM
To: STDS-802-3-YANG@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_YANG] Changes to 802.3 modules in light of IETF actions


(Speaking as a yang doctor)


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. 



Mahesh Jethanandani 

On Jul 19, 2017, at 9:20 PM, Duane Remein <Duane.Remein@xxxxxxxxxx> wrote:

All (but mostly to Rob W),

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?

Best Regards,



Here are relevant drafts: 


And  presentations: (*)




FutureWei Technologies Inc.


Director, Access R&D

Raleigh, NC