As per Relevance of the word possible, we have this rfc below:

---

NWG/RFC# 738 KLH 31 Oct 77 42218
Network Working Group K.
Request for Comments: 738 SRI-
NIC: 42218 31 October 1977



Time




This note describes the Time Server protocol, as currently
on ITS hosts (i.e. MIT-(AI/ML/MC/DMS)). The idea is to provide
site-independent, machine readable date and time in as efficient
swift a manner as possible; its motivation arises from the fact that
all systems have a date/time clock, and all are subject to
human or machine error. The use of time-servers makes it possible
quickly confirm or correct a system's idea of the time, by making
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
a 32-bit socket number to reconnect to, the server returns a 32-bit
value and closes the connection. If the server is unable to
the time at its site, it should either refuse the connection or close
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;
base will serve until the year 2036. As a further example, the
recent leap year as of this writing began from the time 2,398,291,200
which corresponds to 0000 1 Jan 1976 GMT

---

if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.



RFC documents can be found at I.E.T.F.



Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX

---