e: This object represents a set of threshold crossing alert parameters associated with a set of TPs. Topological link (TL): This object represents a physical link between two termination points. Traffic conditioning (TC) profile: This object represents a collection of attri- butes to define the traffic conditioning parameters on a TP. Traffic descriptor (TD): This object represents a collection of attributes used to define bandwidth and quality of service characteristics on a CTP. Transmission descriptor (TMD): This object represents a collection of attri- butes to define multilayered transmission parameters and information param- eters on a TP or MFD. The common attributes shared by these basic objects are: 1. Name: A unique identifier for the object. 2. User label: A user friendly name that shall be provisionable by the NMS. 3. Native EMS name: The name of the object as presented on the EMS GUI. 4. Owner: An identifier for the owner of the object. 5. Additional information: Attributes that has not been explicitly modeled as part of the object. The document defines requirements and use cases based on objects. Also pro- vided in the TMF 513 business agreement is a set of supporting documentation (titled starting with SD) that contain details on various specific aspects of the NML- EML interface and are intended to help clarify some of the specific aspects of the interface that are discussed in the main document (titled staring with TMF513). 8.4 MTNM Information Agreement (TMF 608) Information model is produced prior to the start of implementation of applications, system, and interfaces and it facilitates a requirement agreement between service MTNM Compliant EMS providers and vendors. The TMN608 Interface Information Agreement details a protocol neutral model using UML that includes: Interface problem Interface information requirement Set of interface information use cases Information exchanged over the interface needs to be structured based on the TMF 045 document on common information structure (CIS). CIS detai