tor uses the NW-MO to remove (logi- cally) the logical node n13 (part of a terminal network element) from the traffic network. 1. The WSF/OPF requests removal of n13 ("n13" is the name of a logical node (NN) in the AMLn model here). 2. The NW-MO sees from the AMLn model that the T-RE table of n21 and the T- RO table of n12 must be modified. The NW-MO knows which network ele- ments contain these nodes and which MOs to refer. Consequently it generates suitable requests to the AFs of these elements: removeRouteRequest(n22) affects the T-RE in n21, where the actual route endpoint (REi) is identified by the name of the remote node, in this case n22. 5.6 Summary removeAddressRequest(n13) affects the routing table in n12, where n13 is no longer a possible network address (NA). 3. The referred MOs in the AFs execute these operations by operating on the tables in the traffic plane by proprietary means. An NW-MO will most likely be of a volatile object type, created (on-demand) by an operator request, since all operations that could be performed on the NW- MO most likely are not allowed for all users/operators. In order to protect the man- agement system from accidental or unauthorized actions, operators will have dif- ferent access rights to different operations on the same part of the managed system (in this case the NL1 part). Most operators will have view access to most of the information in the NL1 model, while modifier operations (i.e., operations that can change the state of the traffic system) will be selective, according to some classifi- cation system for operator categories. As a consequence, an operator requesting access to an NW-MO will have to provide the identity of the NL fragment, an access code that identifies the operator category and (possibly) define what kind of management operations are to be per- formed. The network manager (in this case) will check which operations on the fragment that operators of the category have access to, and create a corresponding NW-MO. This might not be the NW-MO the operat