YANG data models represent a contract. The API, generated from the set of YANG modules supported on a device, is as good as the data modules exposed.
If the contract is ambiguous, too long or simply doesn’t represent the data that needs to be exposed by a device, leading to a more severe case, it will affect the YANG consumers (managers, orchestrators, NETCONF clients, etc), and will make interoperability and automation more difficult.
Join us for a FREE webinar on YANG Best Practices, presented by Jan Lindblad, co-author of “Network Programmability with YANG” (Available on Amazon), on June 25th, at 9am PDT.
https://info.tail-f.com/yang-best-practices