Eric S. Raymond esr at thyrsus.com
Tue Sep 25 22:35:43 UTC 2018

James Browning via devel <devel at ntpsec.org>:
> I assume you mean something probably not quite completely unlike.
> * NTS-ke will require listening to a TCP port (possibly 123) and spinning
> up a new thread for each client. (or risk blocking the process)
> * NTS-ke willl require hooks to automtical reconfigure a current NTS key w/
> number a yesterday key w/ number
> * NTS-ke will require a hook to save the above to the ntpkeys file (for
> restarts)
> * NTS-ke will require a hook to update NTS UDP processor
> * NTS will require a hook to hash the standard ntp packet
> * NTS will require the addition of registration of the NTSN KoD packet
> * NTS will require the addition of four? new extension fields.

Correct.  I'm raring to go, but it would be crazy for me to proceed
without a spec that detailed written by someone who already groks
the functional requirements.
		<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.

More information about the devel mailing list