diff options
author | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
---|---|---|
committer | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
commit | 4bfd864f10b68b71482b35c818559068ef8d5797 (patch) | |
tree | e3989f47a7994642eb325063d46e8f08ffa681dc /doc/rfc/rfc738.txt | |
parent | ea76e11061bda059ae9f9ad130a9895cc85607db (diff) |
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc738.txt')
-rw-r--r-- | doc/rfc/rfc738.txt | 59 |
1 files changed, 59 insertions, 0 deletions
diff --git a/doc/rfc/rfc738.txt b/doc/rfc/rfc738.txt new file mode 100644 index 0000000..ae5d6ec --- /dev/null +++ b/doc/rfc/rfc738.txt @@ -0,0 +1,59 @@ + +NWG/RFC# 738 KLH 31 Oct 77 42218 +Network Working Group K. Harrenstien +Request for Comments: 738 SRI-KL +NIC: 42218 31 October 1977 + + + + Time Server + + + + +This note describes the Time Server protocol, as currently implemented +on ITS hosts (i.e. MIT-(AI/ML/MC/DMS)). The idea is to provide a +site-independent, machine readable date and time in as efficient and +swift a manner as possible; its 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. + +In particular the network time server works as follows: + + S: Listen on socket 37 (45 octal). + + U: Connect to socket 37 [not ICP]. + + S: Send the time as a 32 bit binary number. + + U: Close the connection. + + S: Close the connection. + +Note that this is not a normal ICP sequence. Rather, instead of sending +a 32-bit socket number to reconnect to, 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. + +The time is the number of seconds since 0000 (midnight) 1 January 1900 +GMT, such that the time 1 is 12:00:01 am on 1 January 1900 GMT; this +base will serve until the year 2036. As a further example, the most +recent leap year as of this writing began from the time 2,398,291,200 +which corresponds to 0000 1 Jan 1976 GMT. + + + + + + + + + + + + + + [Page 1]
\ No newline at end of file |