RFC 868: Time Protocol
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC868
- Published
- May 1983
- Authors
- J. Postel; K. Harrenstien
- Status
- INTERNET STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 2
- Also known as
- STD26
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 958Network Time Protocol (NTP)Obsoleted
September 1985
- RFC 1059Network Time Protocol (version 1) specification and implementationObsoleted
July 1988
- RFC 1119Network Time Protocol (version 2) specification and implementationObsoleted
September 1989
- RFC 1589A Kernel Model for Precision TimekeepingCurrent
March 1994
- RFC 2030Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSIObsoleted
October 1996
- RFC 2424Content Duration MIME Header DefinitionObsoleted
September 1998
- RFC 2783Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0Current
March 2000
- RFC 2029RTP Payload Format of Sun's CellB Video EncodingCurrent
October 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?