105.09 are as follows: The effects of timing anomalies on SONET payload pointers and their respective payloads Synchronization performance expected during the fault transition from a fully synchronous operation to a worst-case, free-run clocking condition (for example, what clock holdover characteristics are specified for SONET network elements) Stratum compatibility criteria 3.3.4 Maintenance Physical-layer maintenance is accomplished by monitoring the received signals (see Figure 3-30). This figure illustrates the way monitored primitives are used for failure and performance tracking. Near-end events and far-end reports in terms of anomalies, defects, and ANSI T1.416-1999 Figure 3-30 Physical-layer maintenance functions. Physical Receiver layer Framing Near-end defects Far-end defects Payload signal Near-end anomalies SONET Far-end anomalies Near-end Far-end facility events reports Transmitter Failure and performance monitoring Management layer processing, refer to T1.231 Chapter 3 failures are discussed in the following section. Events and reports are used for two purposes: All near-end events and far-end reports will be processed for performance-monitoring primitives and failures, as described in ANSI T1.231. Near-end events will be used to make up far-end reports for the transmitted signal. SONET facilities terminate at three hierarchical levels: Section Maintenance capabilities are performed by SONET network elements and are made possible by maintenance tools built into the overhead fields of the SONET framing structure. Performance monitoring and failure pro- cessing for the physical media, section, line, and path are specified in ANSI T1.231. Near-end events and failures used to make up far-end reports are also specified in ANSI T1.231. Near-end events and failures used to make up far-end reports for the transmitted signal are specified in ANSI T1.105. The near-end events and far-end reports available in SONET are summa- rized in Figure 3-31. Physical Medium STS-1 Rate and Above A loss of signal (LoS) def