On Tue, Sep 5, 2017 at 12:01 PM, Juergen Schoenwaelder < [email protected]> wrote:
> On Tue, Sep 05, 2017 at 11:44:29AM -0700, Andy Bierman wrote: > > > > Blind cut-and-paste is not a good design goal. > > > > Definitions that stand on their own since they are not context > sensitive is IMHO a plus. If I am n pages down a YANG tree and I want > to know whether I look at config false or config true leaves, > searching backwards is really painful if you read on paper (oh, how > old school I am - perhaps this is the issue). Copying a definition > into an email and it stands on its own is a feature I appreciate. Of > course, I understand that others have different preferences. > > > I still don't know what it means to define hierarchical data and say the > > parent is deprecated but not the descendant nodes. > > It is odd but can happen anyway. A current augmentation of something > that got deprecated likely stays current. I would hope that tools warn > if they see this but that's it. > OK > > > This is rather non-intuitive, as is the idea that all descendant > > nodes need to be manually edited (status is not inherited). > > Not a big deal. The benefit is that a reader like me knows clear that > the definition I am look at is deprecated, no need to search backwards > to find out. > OK -- this does not happen too often so it is not a huge impact of writers. > > > It also means the objects expanded from groupings cannot ever be > > changed (clearly a bug in YANG). > > Yes, bug in YANG. > With no way to fix it in RFC 7950 > > > We have not seen these issues yet because this is the first time > > 'status deprecated' is being used. > > Yes. > > /js > Andy > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
