On Wed, 12 Jul 2023, Michael Schapira wrote:
In addition, Kronos' overhead load can easily be reduced further
If Khronos is rolled out as part of an OS with ntp function, and an overloading of the ntp pool happens, it would too late save those ntp nodes. They might remove themselves from the pool, making it even worse for the remaining pool entries. pool.ntp.org is production infrastructure. I still do not see a proper justification for adding Khronos to everything but researcher's machines. The draft really needs to clarify who should run this, and what their benefits are, and who should NOT run this. Ideally, it would recognise when the ntp pool has become overloaded with queries and back off in some way. Paul -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
