* Brad Knowles ([EMAIL PROTECTED]) [050913 16:32] wrote:
>> You're talking about building an OLTP database the likes of which the
>> world has never seen before, and putting that into each and every NTP
>> server in the world.
In "ideal" world run by technical people you are absolutely right.
That's exactly like state of the art solution should look like.
In the very same world ntp pool project's has many servers in every
country in the world, deliver time to all the technical units, from
bridges/routers, servers, desktops to tv-sets, refridgerators,
alarmclocks and wristwatches with subsecond precision.
Thank god we dont live in such world :)
The "problem" for now is sharing list of abusers.
Most/each of ntp pool server admins already gather this data somehow
and already does server protection against abusers somehow.
How it's possible? All those nasty hundreds of milliseconds harddisks
operations delays, firewall accesslists, maybe even traffic inspection
Returning to the scale of operations requirements. Rethoric
questions:
- did ntp pool project had many FTEs since the day one?
- did ntp pool project utilized custom enterprise technologies since the
day one ?
- did ntp pool project had the resources to handle current traffic from
the day one?
And two, out of the air, other rethoric questions concerning possible
blacklist's conduct of operations:
- can ntp servers admins using blacklist utilize the last version
of abusive users list if the blacklist is down ( disappearance
fault-tolerance ) ?
- can abuse records expire automatically to get rid of the manual
records removal ( no helpdesk )
MJ
--
[EMAIL PROTECTED] ( Psyborg ) MJ102-RIPE GTS Polska sp. z o.o.
Servers Administration Department Manager
"Tomorrow is often the busiest time of the year."
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
