Home

NETMOD FAQ

---

Questions related to NMDA:

FAQ related to structuring models to the NMDA style

1. Do all top level containers in a NMDA compliant module have to be "config true" containers?
2. Is an new NMDA compliant module allowed to have a top level "-state" container?
3. When should a transitional "foo-state" module be generate for NMDA compliant module "foo"?
4. How do I generate the transitional "foo-state" module for NMDA compliant module "foo"?

FAQ related to migrating existing model to the NMDA style

1. When is it necessary to wait for updated versions of non-NMDA style published model before updating an augmenting model to conform to NMDA?
2. If we have an non-NMDA draft in progress then is it OK to publish the non NMDA model followed by an NMDA version?
3. Which YANG modules already specified need to be updated to be NMDA compliant?
4. What happens to the old config false "-state" tree in a published YANG module when a NMDA compatible revision is produced?

FAQ related to NMDA implementations

1. What does it mean for a server to be NMDA compliant?
2. In which situations can <intended> differ from <running>?
3. Does an NMDA compliant implementation have to expose the <operational> datastore?
4. Can I find out whether a device has <intended> that can differ from <running>?
5. Does a server have to expose <operational> to be NMDA compliant?
6. Can an NMDA compliant device only support configuration and no operational state?
7. Can an NMDA compliant device only support operational state and not be configurable?
8. What if the device cannot provided an applied configuration value?
9. Are devices allowed to modify the contents of <running>?

---

Questions related to YANG in general:

TBD