This schema was generated from the YANG module controller-network by pyang version 1.2. The schema describes an instance document consisting of the entire configuration data store, operational data, rpc operations, and notifications. This schema can thus NOT be used as-is to validate NETCONF PDUs. identifier for termination points on a port This type is used for leafs that reference topology identifier instance. This type is used for leafs that reference a node instance. This type is used for leafs that reference a link instance. This is the model of abstract topology which contains only Network Nodes and Network Links. Each topology MUST be identified by unique topology-id for reason that the store could contain many topologies. It is presumed that datastore will contain many topologies. To distinguish between topologies it is vital to have UNIQUE topology identifier. The container for definition of topology types. The augmenting modules should add empty optional leaf to this container to signalize topology type. The list of network nodes defined for topology. The Topology identifier of network-node. The Network Link which is defined by Local (Source) and Remote (Destination) Network Nodes. Every link MUST be defined either by identifier and his local and remote Network Nodes (in real applications it is common that many links are originated from one node and end up in same remote node). To ensure that we would always know to distinguish between links, every link SHOULD have identifier. Source node identifier. Destination node identifier.