Re: Year 2000 Compliance

=?ISO-8859-1?Q?Andr=E9_Schild?= ( (no email) )
Fri, 27 Nov 1998 20:23:08 +0100

> We are using SNTPCLNT 1.5 on a Netware 4.10 server. We plan to apply the
> necessary Netware 4.10 patches to make the OS Year 2000 compliant. Is the
> SNTPCLNT 1.5 program Year 2000 Compliant. Does it just do time, or does
> if have date/year issues?
>
V1.5 is Y2K compliant.

NTP timestamps are represented as a 64-bit unsigned
fixed-point number, in seconds relative to 0h on 1 January 1900. The
integer part is in the first 32 bits and the fraction part in the
last 32 bits.

the 64-bit field will overflow some time in 2036 (second
4,294,967,296).

If bit 0 is set, the UTC time is in the range 1968-2036 and UTC time
is reckoned from 0h 0m 0s UTC on 1 January 1900. If bit 0 is not
set, the time is in the range 2036-2104 and UTC time is reckoned
from 6h 28m 16s UTC on 7 February 2036.

As you can see, the (S)NTP protocol is safe up to the year 2104.
Due to some netware API limitations, the NLM will only work
correct up to ~2050.

Y2K tests have showed, that the NLM will work fine up to 2050, but
after this date some problems occured. We have not investigated
on those problems, since they are probably in the Netware libraries
and/or some limitations of the used API calls.

Andre.

MTWIN V3.01, SNTPCLNT V1.1
For new versions http://www.neatech.ch
mailto:ASchild@neatech.ch