amp for seconds, whereas NTP uses several timestamp formats, including one that uses only a 32-bit value for seconds. Therefore, the largest representa- tion for seconds using this NTP timestamp is 232 seconds or 136 years, meaning that there will be a rollover event for NTP during the day of 7 February 2036. The IETF has developed mechanisms to deal with this; see section 6 of RFC 5905 for more details. 7.3 IEEE 1588-2008 (PTPv2) The IEEE 1588-2008 standard defines a protocol for precise synchronization of clocks that commu- nicate with each other over a packet network. At its simplest, the clocks in the network form a mas- ter-slave relationship with one another, during which a master gives timing information to a slave. All clocks in the PTP network ultimately derive their time from the ultimate clock source known as the grandmaster clock (GM clock), which sources its time from a reference clock, such as a satel- lite receiver. Use of the terms "master" and "slave" is ONLY in association with the official terminology used in industry specifications and standards, and in no way diminishes Pearson's commitment to promoting diversity, equity, and inclusion, and challenging, countering and/or combating bias and stereotyping in the global population of the learners we serve. There is no single transport type or encapsulation method defined by PTPv2; rather, it is a toolbox of possible ways to solve the timing synchronization problem. So, the messages being exchanged can be multicast or unicast, layer 2 or layer 3, Ethernet or UDP/IP, or even something else entirely. The goal is to allow heterogeneous systems to get their time from a grandmaster clock, no matter what their implementation, operating system, time accuracy, or cost. Even relatively simple imple- mentations should be able to recover the clock in the microsecond range without a lot of adminis- trative intervention or burdensome management. One important feature of PTPv2 is its extensibility, a capability that allows interested organizations to select onl