 telecom profiles. Almost all operators use a combination of different methods to manage the network devices. The following are some of these methods: A command-line interface (CLI) with a direct connection (via SSH/Telnet) for configuration as well as collecting statistical information and performing troubleshooting. Using proprietary SNMP MIBs, primarily for performance monitoring, as part of an automated management system. The Cisco Evolved Programmable Network Manager (EPNM) is an ex- ample of one such management solution, which provides automation and assurance of SyncE and PTP clocks for Cisco devices. Using the standard NETCONF protocol and proprietary YANG models for configurations, per- formance monitoring, and troubleshooting purposes. Streaming telemetry data from devices for performance monitoring. Other SDOs, such as the IEEE, are also working on YANG data models to supplement their existing specifications for PTP. Two projects are currently underway: P1588e: The organization responsible for 1588 is working on several amendments to the 1588- 2019 version. The focus of this specific project, P1588e, is to specify MIB and YANG data models for all PTP datasets included in the 1588 standard. The goal is to produce module files that specify the MIB and YANG data models and make them publicly accessible. P802.1ASdn: The organization responsible for the 802.1 1AS PTP profile has a project to define a YANG data model for the 2020 versions of that PTP profile. The goal is to allow configura- tion and reporting of all managed objects in the base standard. As many of the managed objects in 802.1AS originate from 1588, it makes sense that this model will augment the model from P1588e. For further information on both these projects, refer to their references in the section "Further Read- ing" at the end of the chapter. It is the authors' opinion that the automation and assurance aspects of both SyncE and PTP are be- ginning to evolve and will proceed rather quickly. Standardization activities on this front are on