Syncing Time Critical Processes Using NTP
By: Dave | Posted: 08th May 2008
The Network Time Protocol (NTP) was developed more than 25 years ago to synchronise Internet servers to the correct time. NTP is now one of the oldest protocols still in operation today. The protocol is widely used to synchronise Internet and intranet infrastructure and processes. This article briefly outlines the operation of NTP and some of the terminology associated with the protocol.
NTP was originally developed to solve the requirement of synchronisation of critical time processes across the Internet. The Network Time Protocols primary platform is the LINUX operating system. NTP is provided under the GNU public licence; however, it has also been sucessfully ported to the Windows operating system. NTP is most widely used on LINUX as many of the algorithms needed to provide precise time are embedded into its kernel.
NTP is based upon the User Data-gram Protocol (UDP) which is in-turn reliant on the TCP/IP protocol. It communicates using UDP port 123, which is reserved solely for use by NTP. The protocol basically consists of a number of fields, which specify: clock-offset, round-trip delay and dispersion relative to a precise time source. The information stored in each NTP packet allow a network time client to accurately synchronise time with a NTP server.
NTP is a structured protocol that operates in a hierarchical manner. At the top of the tree, a primary time reference is known as a stratum 1 time server. Servers that synchronise to a stratum 1 server are known as stratum 2 servers and so on down each level of the hierarchy. As the stratum increases, so generally precision decreases.
Over a number of years NTP has been enhanced to operate with a plethora of precision hardware clock devices, or reference clocks. NTP reference clocks are available for GPS hardware and also many of the National Radio Time and Frequency standards such as MSF, DCF-77 and WWVB. Many hardware reference clocks also provide backup precision timing outputs such as TCXO, OCXO and rubidium references to maintain accurate time in the event of signal loss.
A spin-off of the NTP protocol is SNTP or Simple Network Time Protocol, which is basically as the name implies, a simplified version of NTP. SNTP is generally used in small low-powered computing devices such as micro-controllers. It allows low-powered devices the ability to synchronise time to NTP servers over a network.
To summarise, NTP is a long-standing and widely used protocol for synchronising time between time critical processes. NTP has a linear heirarchical structure that can provide a timing resource for large numbers of clients. For applications that require critical timing, NTP provides a de-facto standard solution.
------
D. Evans is an experienced technical author in the field of NTP and precision timing references. David is the auther of many white-papers and articles detailing the installation of computer network timing equipment. Please click here, if you would like more information on NTP Server systems.
This article is free for republishing
Printed From: http://www.articlealley.com/article_534180_45.html
Back to the original article
Tags: windows operating system, network time protocol, correct time, linux operating system, internet servers, ntp server