nd on how the actual management system defines the concept of "managed object." There is SO far no common view on this 5 Management and Traffic Systems regarding the standards mentioned. Consequently each management standard defines its own mpCP abstract protocol. In AMLn we do not provide any generic operation definitions for mpCPs since they would not differ much from existing standards (e.g., CMIS/CMP and SNMP). Let's instead look more generally on which type of operations may be needed in MO-oriented mpCP protocols. An AF will at any time include a large set of object instances (MOs) of different object classes. The things you (as an OSF) may want the AF to do can be listed as follows (this list corresponds more or less to the defi- nition of "services" in CMIS): GET information about the state of traffic system resources. Since real resources are represented by MOs, this information is represented by a single MO or by a set of MOs. The request-ASP must therefore include parameters that identify either an individual MO (by an object identifier) or a set of MOs. It also defines the attributes of the MO class it wants to read. The operation may provide infor- mation about the time when the information was read, and when a certain attribute was last changed. GET operations must be operations of the AMLs operation class REQUEST. Note that GET operations do not change anything in the traffic plane, i.e., the state of the traffic plane is not changed. In AMLs we call such operations selec- tor operations. SET attribute values of existing MOs. This operation may be used for initiating MOs, for specializing MOs according to attributes in the MO class, or for setting an MO in a particular state. A SET operation may be of class ORDER or REQUEST. A SET operation also does not change anything in the traffic plane. In AMLs we call such operations initiator operations. CREATE a new MO instance. A CREATE operation must be of class REQUEST. A CREATE operation increases the range of management performed via the management sys