1 // vi: set smarttab sw=4 tabstop=4:
2 module abstract-topology {
7 import ietf-inet-types { prefix "inet"; }
8 import abstract-prefixes { prefix "abs-pref"; }
12 contact "WILL-BE-DEFINED-LATER";
15 This module contains the definitions of elements that creates network
16 topology i.e. definition of network nodes and links. This module is
17 not designed to be used solely for network representation. This module
18 SHOULD be used as base module in defining the network topology.
21 revision "2013-02-08" {
22 reference " WILL BE DEFINED LATER";
25 revision "2013-03-08" {
26 reference " WILL BE DEFINED LATER";
29 revision "2012-02-08" {
30 reference " WILL BE DEFINED LATER";
33 typedef topology-id-ref {
35 path "/tp:topology/tp:topology-id";
37 description "This type is used for leafs that reference topology identifier instance.";
40 typedef network-node-id-ref {
42 path "/tp:topology/tp:network-nodes/tp:network-node/tp:node-id";
44 description "This type is used for leafs that reference network node instance.";
49 path "/tp:topology/tp:network-links/tp:network-link/tp:link-id";
51 description "This type is used for leafs that reference network link instance.";
56 This is the model of abstract topology which contains only Network
57 Nodes and Network Links. Each topology MUST be identified by
58 unique topology-id for reason that the store could contain many
65 It is presumed that datastore will contain many topologies. To
66 distinguish between topologies it is vital to have UNIQUE
71 container network-nodes {
73 description "The list of network nodes defined for topology.";
79 description "The Topology identifier of network-node.";
82 container attributes {
84 Additional attributes that can Network Node contains.
90 container network-links {
93 The Network Link which is defined by Local (Source) and
94 Remote (Destination) Network Nodes. Every link MUST be
95 defined either by identifier and his local and remote
96 Network Nodes (in real applications it is common that many
97 links are originated from one node and end up in same
98 remote node). To ensure that we would always know to
99 distinguish between links, every link SHOULD have
112 description "Source node identifier.";
116 container destination {
119 description "Destination node identifier.";
123 container attributes {
124 description "Aditional attributes that can Network Link contains.";
130 //TODO: add base operations