TIME protocol
From Wikipedia, the free encyclopedia
| The five layer TCP/IP model |
| 5. Application layer |
|
DHCP • DNS • FTP • HTTP • IMAP4 • IRC • NNTP • XMPP • MIME • POP3 • SIP • SMTP • SNMP • SSH • TELNET • BGP • RPC • RTP • RTCP • TLS/SSL • SDP • SOAP • L2TP • PPTP • … |
| 4. Transport layer |
| 3. Network layer |
| 2. Data link layer |
|
ATM • DTM • Ethernet • FDDI • Frame Relay • GPRS • PPP • ARP • RARP • … |
| 1. Physical layer |
|
Ethernet physical layer • ISDN • Modems • PLC • SONET/SDH • G.709 • Wi-Fi • … |
The TIME service is an Internet protocol defined in RFC 868. Its purpose is to provide a site-independent, machine readable date and time.
TIME can operate over either TCP or UDP. When operating over TCP, a host connects to a server that supports the TIME protocol on TCP port 37. The server then sends the time as a 32-bit binary number in network byte order representing a number of seconds since 00:00 (midnight) 1 January, 1900 GMT. The host receives the time and closes the connection.
When operating over UDP, the client sends a (typically empty) datagram to UDP port 37. The server responds with a single datagram of length 4 containing the time. There is no connection setup or teardown.
In modern practice, the TIME protocol is completely superseded by the Network Time Protocol (NTP).
On Linux, FreeBSD, and other UNIX-like operating systems a time server is built into the inetd daemon. The time service is usually not enabled by default. It may be enabled by adding the following lines to the file /etc/inetd.conf and telling inetd to reload its configuration:
time stream tcp nowait root internal time dgram udp wait root internal