nformation about Multi Layer Sub Network Link information. It also supports assign/ de-assign of signaling controller and set/modify actions related to signaling protocol and parameters. TrafficDescriptorMgr_I: The NMS uses this interface to request information about traffic descriptors (bandwidth and quality parameters). It should be noted that the TrafficDescriptor_T object is obsolete according to the latest definitions in TMF814. A few examples of managed objects handled by the managers are: EMS manager (EMSMgr) is associated with EMS object, MLSN object, alarm object, topological link object, and SO on. Equipment manager (EquipmentInventoryMgr) is associated with equipment object, equipment holder object, and SO on. Managed element manager (ManagedElementMgr) is associated with man- aged element object, termination point object, alarm object, MLSN object, and SO on. The key session related interfaces are: EmsSessionFactory_I: This interface is the first instance used by the NMS to communicate with EMS. It is registered with the naming service and requires a user name and password to access the EMS. EmsSession_ This interface is used to find interoperable object reference (IOR) for interfaces supported by the EMS including the notification service. NmsSession_I: This interface is supported by the NMS and used by EMS, unlike other interfaces, which are supported by EMS and used by NMS. This interface allows the EMS to notify the NMS about events like loss of alarms. MTNM Compliant EMS When a list of items is returned in response to a request from the NMS, an iterator interface can be used to retrieve items from a list. The iterator instance is destroyed after the client has finished retrieving data. Example: EquipmentOr HolderIterator_I The CORBA services that are intended to be used along with TMF814 are: Naming service: It involves mapping objects with a hierarchical naming structure. So that names can be used instead of objects in making queries for a specific interface. The server binds the object and name