Katana VentraIP

Network Time Protocol

The Network Time Protocol (NTP) is a networking protocol for clock synchronization between computer systems over packet-switched, variable-latency data networks. In operation since before 1985, NTP is one of the oldest Internet protocols in current use. NTP was designed by David L. Mills of the University of Delaware.

Not to be confused with Daytime Protocol, Time Protocol, or NNTP.

International standard

David L. Mills, Harlan Stenn, Network Time Foundation

1985 (1985)

NTP is intended to synchronize all participating computers to within a few milliseconds of Coordinated Universal Time (UTC).[1]: 3  It uses the intersection algorithm, a modified version of Marzullo's algorithm, to select accurate time servers and is designed to mitigate the effects of variable network latency. NTP can usually maintain time to within tens of milliseconds over the public Internet, and can achieve better than one millisecond accuracy in local area networks under ideal conditions. Asymmetric routes and network congestion can cause errors of 100 ms or more.[2][3]


The protocol is usually described in terms of a client–server model, but can as easily be used in peer-to-peer relationships where both peers consider the other to be a potential time source.[1]: 20  Implementations send and receive timestamps using the User Datagram Protocol (UDP) on port number 123.[4][5]: 16  They can also use broadcasting or multicasting, where clients passively listen to time updates after an initial round-trip calibrating exchange.[3] NTP supplies a warning of any impending leap second adjustment, but no information about local time zones or daylight saving time is transmitted.[2][3]


The current protocol is version 4 (NTPv4),[5] which is backward compatible with version 3.[6]

Timestamps[edit]

The 64-bit binary fixed-point timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving a time scale that rolls over every 232 seconds (136 years) and a theoretical resolution of 2−32 seconds (233 picoseconds). NTP uses an epoch of January 1, 1900. Therefore, the first rollover occurs on February 7, 2036.[35][36]


NTPv4 introduces a 128-bit date format: 64 bits for the second and 64 bits for the fractional-second. The most-significant 32 bits of this format is the Era Number which resolves rollover ambiguity in most cases.[37] According to Mills, "The 64-bit value for the fraction is enough to resolve the amount of time it takes a photon to pass an electron at the speed of light. The 64-bit second value is enough to provide unambiguous time representation until the universe goes dim."[38][b]

t0 is the client's timestamp of the request packet transmission,

t1 is the server's timestamp of the request packet reception,

t2 is the server's timestamp of the response packet transmission and

t3 is the client's timestamp of the response packet reception.: 19 

[1]

A typical NTP client regularly polls one or more NTP servers. The client must compute its time offset and round-trip delay. Time offset θ is positive or negative (client time > server time) difference in absolute time between the two clocks. It is defined by


and the round-trip delay δ by where


To derive the expression for the offset, note that for the request packet, and for the response packet, Solving for θ yields the definition of the time offset.


The values for θ and δ are passed through filters and subjected to statistical analysis ("mitigation"). Outliers are discarded and an estimate of time offset is derived from the best three remaining candidates. The clock frequency is then adjusted to reduce the offset gradually ("discipline"), creating a feedback loop.[1]: 20 


Accurate synchronization is achieved when both the incoming and outgoing routes between the client and the server have symmetrical nominal delay. If the routes do not have a common nominal delay, a systematic bias exists of half the difference between the forward and backward travel times. A number of approaches have been proposed to measure asymmetry,[39] but among practical implementations only chrony seems to have one included.[40][41]

Ntimed was started by of FreeBSD in 2014 and abandoned in 2015.[62] The implementation was sponsored by the Linux Foundation.[63]

Poul-Henning Kamp

systemd-timesyncd is the SNTP client built into . It is used by Debian since version "bookworm"[64] and the downstream Ubuntu.

systemd

Leap seconds[edit]

On the day of a leap second event, ntpd receives notification from either a configuration file, an attached reference clock, or a remote server. Although the NTP clock is actually halted during the event, because of the requirement that time must appear to be strictly increasing, any processes that query the system time cause it to increase by a tiny amount, preserving the order of events. If a negative leap second should ever become necessary, it would be deleted with the sequence 23:59:58, 00:00:00, skipping 23:59:59.[65]


An alternative implementation, called leap smearing, consists in introducing the leap second incrementally during a period of 24 hours, from noon to noon in UTC time. This implementation is used by Google (both internally and on their public NTP servers), Amazon AWS,[66] and Facebook.[67] Chrony supports leap smear in smoothtime and leapsecmode configurations, but such use is not to be mixed with a public NTP pool as leap smear is non-standard and will throw off client calculation in a mix.[68]

Allan variance

Clock network

International Atomic Time

IRIG timecode

NITZ

NTP pool

Ntpdate

Precision Time Protocol

. doi:10.17487/RFC5907. RFC 5907.

Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)

. doi:10.17487/RFC5908. RFC 5908.

Network Time Protocol (NTP) Server Option for DHCPv6

Edit this at Wikidata

Official website

Official Stratum One Time Servers list

IETF NTP working group

and more

Microsft Windows accurate time guide

Time and NTP paper

NTP Survey 2005

Current NIST leap seconds file compatible with ntpd

David L. Mills, (PDF), retrieved 2021-02-07

A Brief History of NTP Time: Confessions of an Internet Timekeeper