aulty The port is in a fault state and ignored, although it can send management messages. Disabled Any traffic on this port is ignored except for management messages. The port is listening for an Announce message, although it can send peer-delay, signaling, and Listening management messages. The port is behaving as a master but not sending timing messages, although it can send peer-delay, Pre_master signaling, and management messages. Master The port is sending timing information and Announce messages to downstream slaves. Passive The port is not sending timing messages, although it can send peer-delay, signaling, and manage- ment messages. Uncalib- A master port has been detected and selected, and the local port is preparing to synchronize to that rated port. Slave The port is being synchronized by a selected master port. Under normal operations, the deployment engineer would most likely see the states of master, pass- live, and slave, as the other states are mostly transient (unless something goes wrong). When the PTP node is initialized, then the PTP ports are all in the initializing state as the timing system prepares itself, fills the data structures, and prepares the communications paths. Then, the ports should go into listening state, whereby they listen for Announce messages to determine what master clock they can synchronize with. Then, as the master is selected, the highest-priority port will go through uncalibrated before entering slave state. As the PTP node becomes phase aligned to the remote master, the other ports may become master (to a downstream slave) or passive (neither a master to another clock nor synchronized to a master). 7.3.1 Transport and Encapsulation The IEEE 1588-2008 standard defines numerous methods of transporting and encapsulating PTP messages, which are outlined in the Annexes to the standard shown in Table 7-4. Note that the equi- valent sequence of Annexes in IEEE 1588-2019 have been reduced by one, SO that they start at An- nex C. Table 7-4 PTP Transport and Encapsulation Tra