Hi, this was intended as an example. The reason to include the interfaces module is the scenario in which a controller would like to have a model/inventory of the various interfaces across the network. Each network device will have its own instantiation of the interfaces module. Rather than replicating interfaces information in a network controller model, by mounting this data under the corresponding network element’s list element, the need to re-define interface data (just to be included in a different place in the containment hierarchy) is avoided.
Hope that helps --- Alex (just returning from holiday break, hence the delayed response) From: netmod [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, December 22, 2015 3:45 AM To: [email protected] Subject: [netmod] Draft clemm netmod mount draft In the controller-network data model , is the interfaces module imported for a specific reason ? Sent from Outlook Mobile<https://aka.ms/blhgte>
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
