Hal Murray via devel <devel@ntpsec.org>:
>
> Achim said:
> > No. What the heck is an NTS client supposed to be?
>
> > There is no separation of NTS and NTP server either, an NTS server is
> > supposed to answer plain NTP clients with the old style NTP packets.
>
> I think there is confusion on the names and/or the way chunks of code get
> packaged.
>
> NTS is short for NTS-KE, not a NTP that supports NTS, NTP is short for a
> system that supports NTP with NTS and probably old NTP requests too.
>
> The current ntpd is both client and server. The diagram shows them in
> separate boxes. Note that the NTP client talks to a NTP server in a
> different
> system so there has to be some communication.
Achim, I confirm that Hal is correct in all of this.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
