Synchronisation of computer clocks across networks
Many implementations exist for time synchronisation between computers over a network. Below you will find a short list of popular network protocols which are in use today:
(RFC 867) protocol sends a human readable string when connecting to UDP or TCP port 13
# telnet time.nist.gov 13
Connected to time.nist.gov.
Escape character is '^]'.
53242 04-08-25 17:54:30 50 0 0 735.3 UTC(NIST) *
Connection closed by foreign host.
(RFC 868) protocol is similar to the daytime protocol described above and used by for example rdate and FG Time Sync
(win). The format of the time given by the time server is in "computer readable" format.
daemon uses ICMP messages for time synchronization. Most routers and hosts don't support ICMP timestamp requests.
(RFC 1305, RFC 2030, http://www.ntp.org
) is the most popular time synchronization protocol in use nowadays. NTP has good accuracy (milliseconds across Internet and microseconds or less in LAN environments) with only little network traffic.
The time synchronization problem
Why would anybody need another time protocol, when ntp is already great?
A simple answer is "you don't", unless you don't have access to a ntp server, because you are behind a firewall and/or proxy server.
In order for ntp to work, you need to have access to outgoing and incoming packets from UDP port 123. In most corporate environments this is not the case and you must consider yourself lucky if you have Internet access via an HTTP proxy server. As long as HTTP or HTTPS connectivity is available, you can use HTP.