Browse Prior Art Database

Time Protocol (RFC0868)

IP.com Disclosure Number: IPCOM000003916D
Original Publication Date: 1983-May-01
Included in the Prior Art Database: 2019-Feb-14
Document File: 3 page(s) / 3K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Postel: AUTHOR [+1]

Related Documents

10.17487/RFC0868: DOI

Abstract

This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Time Protocol are expected to adopt and implement this standard. This protocol provides a site-independent, machine readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 65% of the total text.

Network Working Group J. Postel - ISI Request for Comments: 868 K. Harrenstien - SRI May 1983

Time Protocol

This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Time Protocol are expected to adopt and implement this standard.

This protocol provides a site-independent, machine readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900.

One motivation arises from the fact that not all systems have a date/time clock, and all are subject to occasional human or machine error. The use of time-servers makes it possible to quickly confirm or correct a system’s idea of the time, by making a brief poll of several independent sites on the network.

This protocol may be used either above the Transmission Control Protocol (TCP) or above the User Datagram Protocol (UDP).

When used via TCP the time service works as follows:

S: Listen on port 37 (45 octal).

U: Connect to port 37.

S: Send the time as a 32 bit binary number.

U: Receive the time.

U: Close the connection.

S: Close the connection.

The server listens for a connection on port 37. When the connection is established, the server returns a 32-bit time value and closes the connection. If the server is unable to determine the time at its site, it should either refuse the connection or close it without sending anything.

Postel [Page 1]

RFC 868 May 1983 Time Protocol

When used via UDP the time service works as follows:

S: Listen on port 37 (45 o...

Processing...
Loading...