NTP Protocol
NTP Protocol
KENGNE NICK
INTRODUCTION
NIST estimates 10-20 million NTP severs and clients deployedin the
02 internetand its tributaries all over the world. Every Windows/Xp has an
NTP client
04 NTP software has been ported to almost every workstation and server
platform available today - from PCs to Crays -Unix, Windows, CMS and
embedded systems, even home routers and battery backup systems.
❖ USNO and NIST, as well as equivalents in other countries, provide multiple NTP primary servers directly synchronized to
national standard cesium clock ensembles and GPS
❖ Over 230 internet primary servers are in Australia, Canada, Chike, Franxce, Germany, Israel, Italy, Holland, Japan, Norway,
sweden, switzerland, UK, and US
02 Well over a million Internet servers and clients are all over the world
❖ National and regional service providers BBN, MCI, Sprint, Alternet, etc
❖ Agencies and organizations: US Weather Service, US Treasury Service, IRS, PBS, Merril Lynch, Citicorp, GTE, Sun, DEC,
HP, etc
❖ Private networks are reported to have over 10,000 NTP servers and clients behind firewalls; one (GTE) reports in the order of
30,000 NTp workstations and PCs
❖ NTP has been on the NASA shuttle and in Antarctica and planned for the Mars Internet.
Needs for precision time
Goals
01 ❖ Provide the best accuracy under prevailing network and server conditions.
❖ Resist many and varied kinds of failures, including two-face, fail-stop, malicious attacks and implementation bugs.
❖ Maximize utilization of Internet diversity and redundancy.
❖ Automatically organize subnet topology for best accuracy and reliability.
❖ Self contained cryptographic authentication based on both symmetric key and public key infrastructures and independent of
external services.
02 Non-goals
04 ❖ For each new server found, fetch and verify its cryptographic
credentials.
❖ Authenticate each message received using engineered protocol.
❖ Regenerate keys in a timely manner to resist compromise.
A day in the life of a busy NTP server
❖ NTP primary (stratum 1) server rackety is a Sun IPC running SunOS
4.1.3 and supporting 734 clients scattered all over the world
❖ This machine supports NFS, NTP, RIP, IGMP and a mess of printers,
radio clocks and an 8-port serial multiplexor
❖ The mean input packet rate is 6.4 packets/second, which corresponds
to a mean poll interval of 157 seconds for each client
❖ Each input packet generates an average of 0.64 output packets and
requires a total of 2.4 ms of CPU time for the input/output transaction
❖ In total, the NTP service requires 1.54% of the available CPU time and
generates 10.5, 608-bit packets per second, or 0.41% of a T1 line
❖ The conclusion drawn is that even a slow machine can support
substantial numbers of clients with no significant degradation on other
network services
Reference clock sources (1997 survey)
In a survey of 36,479 peers, found 1,733 primary and backup external
01 reference sources
02 1,502 local clock backup sources (used only if all other sources fail)
Multicast
01 ❖
❖
❖
For high speed networks
High Accuracies are not required
Time Servers send periodic NP broadcasts
❖ Determine the time based on an assumed delay
❖ Time servers provides synchronization, but do not accept NTP messages from clients
Procedure-Call
02 ❖
❖
❖
Intended for file servers or workstations that require high evels of accuracy
A Time Server acting as a client send a request to a peer operating as a server
Server after inserting timestamps and recalculating the Checksum, sends back the message
❖ A server operating as a client can be synchronized, but cannot provide synchronization
❖ A server operating as a server can provide synchronization, but cannot be synchronized
Symmetric
03 ❖ A server can provide synchronization or to be synchronized
❖ Two modes of operation:
• Active Mode: For servers in the high levels of the stratum (near the leaves)
Passive Mode: For servers in the low levels of thestratum (near the root)
NTP onl ine resources a t www.n tp .org