Origin timestamp: A timestamp from the originating node within +1 second. This is not like a timestamp in an event message, as it is not really time sensitive, although the format is the same. Therefore, the timestamp consists of a 6-byte (48-bit) seconds field, with a 4-byte (32-bit) nanoseconds field. Current UTC offset: Total number of leap seconds currently in effect (37 as of 2021). In com- bination with an accurate timestamp based on TAI, this allows the PTP clock to accurately cal- culate an estimate for UTC. Grandmaster priority1: Value in range 0-255 used as a priority order for GM clock selection, whereby lower values are higher priority. The allowable range can vary (or be fixed at a specific value) when specified by a PTP profile. Grandmaster clock quality: Made up of three separate values that indicate the inherent accur- acy of the grandmaster; the traceability of the grandmaster to a time source; and the accuracy of that time (total of 32 bits). See the following list for a detailed breakdown. Grandmaster priority2: Value in range 0-255, used as a tiebreaker in GM clock selection when priority] values agree. As with priority1, lower values are higher priority, and the allow- able values can be varied by a profile. Grandmaster identity: A 64-bit address clockIdentity that is either an IEEE extended unique identifier (EUI-64) individually assigned number or some constructed value (see IEEE 1588- 2008 section 7.5.2.2). This should be a unique number that can act as the final tiebreaker for the BMCA. Steps removed: stepsRemoved is a count of the number of BC steps from the grandmaster. Every time the PTP flow is passed through a BC, the steps removed count is increased by one. Time source: timeSource is a value that indicates the GM's source of time, such as GPS, NTP, ATOMIC_CLOCK, or INTERNAL OSCILLATO (see IEEE 1588-2008 section 7.6.2.6 for all possible values of 16-bit value). GPS refers to any of the GNSS systems rather than having to be specifically GPS. The grandmaster clock accuracy field is mad