-
Improvement
-
Resolution: Done
-
Medium
-
None
We are currently using two EffectiveModelContexts to execute baseline NETCONF requests – one without notifications and one with notifications.
Neither of these correspond exactly to the NETCONF device baseline, as we do not consider advertized capabilities to actually construct them.
Rework BaseSchemas to use an accurate EffectiveModelContext based on the advertized capabilities.
- blocks
-
NETCONF-80 RPC POST to yang-ext:mount doesn't support XML Attributes
- Confirmed
-
NETCONF-806 get-config/edit-config not working for netopeer2 devices
- Confirmed
- relates to
-
NETCONF-840 YANG1.1 modules with submodules unavailabe because ietf-yang-library not used
- In Progress
-
NETCONF-1233 Blocking call during NetconfDeviceSchemas acquisition
- Resolved