Dhruv, the question is very broad and hence difficult to answer. Some things to consider:
For certain events that a system will detect and handle anyway and that are generally relevant for management applications (an interface going up or down for example), having a specific notification defined will likely remain useful. You also have to consider whether all systems implementing your data model can be expected to implement the push and subscription models. Despite implementation costs, these models come with a certain runtime overhead as well. /js On Wed, Jul 19, 2017 at 01:09:53PM +0530, Dhruv Dhody wrote: > > Hi WG, > > As suggested by Lou, I am posting the question to the WG list with a > suggestion that perhaps such a guideline could be addressed in 6087bis. > > My question to yang doctors regarding the Notification was - > > What is the guideline for including Notification in the Yang model, now > that [I-D.ietf-netconf-yang-push] and > [I-D.ietf-netconf-subscribed-notifications] is the preferred approach? > > Should we keep only "mandatory to implement notifications" in the Yang > model? Or just remove the notifications completely? > > A guideline to model writers would be helpful here, IMHO. > > Regards, > Dhruv > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod -- 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 netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
