Impact analysis of ietf-network, showing the scope of work which is being done on top of these models:

https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-network-topology&recurse=3&rfcs=1&show_subm=0&show_dir=dependents

Some concerns were risen today around the user impact and amount of work for this change. Would it be possible to know:

• Summary of API changes introduced by this model update.
• Estimated work to migrate key projects listed above.

The model changes very few things in real terms:

• there are two models, ietf-network (i.e. inventory equivalent) and ietf-network-topology
• a change in namespace, hence a change in imports
• NetworkTopology, Topology, TopologyId, TopologyKey -> Networks, Network, NetworkId, NetworkKey
• Structural comparison can easily be draw from comparing these sections:
  • Old: https://tools.ietf.org/html/draft-clemm-netmod-yang-network-topo-01#section-3.2
  • New: https://tools.ietf.org/html/rfc8345#section-4

In terms on time – NETCONF took ~8 hours to migrate, including UTs and adjustment of SFC to cope and an update to the model (which broke the patch again).