|
The Network Time Protocol (NTP) is a protocol for synchronizing the clocks of computer systems over packet-switched, variable-latency data networks. NTP uses UDP port 123 as its transport layer. It is designed particularly to resist the effects of variable latency. NTP is one of the oldest Internet protocols still in use (since before 1985). NTP was originally designed by Dave Mills of the University of Delaware, who still maintains it, along with a team of volunteers. NTP is not related to the much simpler DAYTIME (RFC 867) and TIME (RFC 868) protocols.
Overview NTP uses Marzullo's algorithm with the UTC time scale, including support for features such as leap seconds. NTPv4 can usually maintain time to within 10 milliseconds (1/100 s) over the public Internet, and can achieve accuracies of 200 microseconds (1/5000 s) or better in local area networks under ideal conditions. The NTP Unix daemon is a user-level process that runs continuously on a machine that supports NTP, and most of the protocol is implemented in this user process. To get the best performance from NTP, it is important to have the standard NTP clock phase-locked loop implemented in the operating system kernel, rather than using only the intervention of the external NTP daemon: all recent versions of the Linux and Solaris operating systems have this support. The operational details of NTP are illustrated in RFC 778, RFC 891, RFC 956, RFC 958, and RFC 1305. The current reference implementation is version 4 (NTPv4); however, as of 2005, only versions up to 3 (1992) have been documented in RFCs. The IETF NTP Working Group has formed to standardize the work of the NTP community since RFC 1305 et al. A less complex form of NTP that does not require storing information about previous communications is known as the Simple Network Time Protocol or SNTP. It is used in some embedded devices and in applications where high accuracy timing is not required. See RFC 1361, RFC 1769, RFC 2030 and RFC 4330. Clock strata (Note that this is different from the notion of clock strata used in telecommunications systems.) NTP uses a hierarchical system of "clock strata". The stratum levels define the distance from the reference clock and the associated accuracy. NTP timestamps The 64-bit timestamps used by NTP consist of a 32-bit seconds part and a 32-bit fractional second part with an epoch of January 1, 1970, giving NTP a time scale of 232 seconds (136 years) and a theoretical resolution of 2−32 seconds (0.233 nanoseconds). Although the NTP timescale wraps around every 232 seconds, implementations should disambiguate NTP time using a knowledge of the approximate time from other sources. Since this only requires time accurate to a few decades, this unlikely to ever be a problem in general use. Even so, future versions of NTP will extend the time representation to 128 bits – 64 bits for the second and 64 bits for the fractional-second. According to Mills, "The 64 bit value for the fraction is enough to resolve the amount of time it takes a proton to pass an electron. The 64 bit second value is enough to provide unambiguous time representation until the universe goes dim." See also Other time synchronization protocols | ||||||||
|
| |||||||||
 |
|
| |