A Subnetwork Connection relates end-point TPs or GTPs. All end point TPs related by an SNC must support the same or an equivalent layer rate which is also the SNC's layer rate. A SNC provides a transparent end-to-end connection or a trail (closed or half-open) through a Subnetwork according to the roles associated to its end points. If it represents a connection, its end points are Connection Termination Points (CTPs) or Floating Termination Points (FTPs) with the SNC's layer rate as connectable layer rate. If it represents a trail, its end points are CTPs or FTPs or Physical Termination Points (PTPs).
In pending state, generic connection termination point(s) of the SNC could be replied.
Refer to the associated supporting document snctypes for explanation of SNC Properties, SNC Parameters, unidirectional SNCs,  Point-to-Multipoint SNC, Routing Constraints and Route Discovery.

MTOSI Specific Documentation
This class is applicable to MTOSI. The specific operations and relationships that apply to MTOSI are listed in SD2-11. 
For MTOSI, references to "NMS" can be interpreted as "Requesting OS" and references to "EMS" can be interpreted as "Target OS", i.e., the OS that fulfills requests from another OS. 
The statements concerning Object Lifecycle, i.e., whether the object can be created by the NMS or EMS, are not particularly meaningful for MTOSI, since MTOSI does not define management systems with fixed roles such as the NMS and EMS entities in MTNM.

Object Lifecycle: Created and deleted by NMS, using methods on the containing Subnetwork object, or by EMS.

Object Creation Notification Issued? Yes
Object Deletion Notification Issued? Yes
Object Discovery Notification Issued? Yes
