Time Protocol
The Time Protocol is a network protocol in the Internet Protocol Suite. Its purpose is to provide a site-independent, machine readable date and time. The Time Protocol may be implemented over the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP). A host connects to a server that supports the Time Protocol on port 37. The server then sends the time as a 32-bit unsigned integer in binary format and in network byte order, representing the number of seconds since 00:00 (midnight) 1 January 1900 GMT, and closes the connection. Operation over UDP requires the sending of any datagram to the server port, as there is no connection setup for UDP. The fixed 32-bit data format means that the timestamp rolls over approximately every 136 years, with the first such occurrence on 7 February 2036. Programs that use the Time Protocol must be carefully designed to use context-dependent information to distinguish these dates from those in 1900. Many Unix-like operating systems used the Time Protocol to monitor or synchronize their clocks using the rdate utility, but this function was superseded by the Network Time Protocol (NTP) and the corresponding ntpdate utility. NTP is more sophisticated in various ways, among them that its resolution is finer than one second.
| Internet protocol suite |
|---|
| Application layer |
| Transport layer |
| Internet layer |
| Link layer |
The Time Protocol is a network protocol in the Internet Protocol Suite.[1] Its purpose is to provide a site-independent, machine readable date and time.
The Time Protocol may be implemented over the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP). A host connects to a server that supports the Time Protocol on port 37. The server then sends the time as a 32-bit unsigned integer in binary format and in network byte order, representing the number of seconds since 00:00 (midnight) 1 January 1900 GMT, and closes the connection. Operation over UDP requires the sending of any datagram to the server port, as there is no connection setup for UDP.
The fixed 32-bit data format means that the timestamp rolls over approximately every 136 years, with the first such occurrence on 7 February 2036. Programs that use the Time Protocol must be carefully designed to use context-dependent information to distinguish these dates from those in 1900.
Many Unix-like operating systems used the Time Protocol to monitor or synchronize their clocks using the rdate utility, but this function was superseded by the Network Time Protocol (NTP) and the corresponding ntpdate utility. NTP is more sophisticated in various ways, among them that its resolution is finer than one second.
Inetd implementation
[edit]On most UNIX-like operating systems a Time Protocol server is built into the inetd (or xinetd) daemon. The service is usually not enabled by default. It may be enabled by adding the following lines to the file /etc/inetd.conf and reloading the configuration.
time stream tcp nowait root internal time dgram udp wait root internal
See also
[edit]- Echo Protocol
- Discard Protocol
- Daytime Protocol
- Character Generator Protocol
- rdate, a tool for querying the current time from a network server
External links
[edit]References
[edit]- ^ J. Postel; K. Harrenstien (May 1983). Time Protocol. Network Working Group. doi:10.17487/RFC0868. STD 26. RFC 868. Internet Standard 26.