[ntpwg] KISS codes

[anthony.flavin at bt.com]

That doesn't work.

For a busy server the client list is being updated all the time, so the
list is not static. So how do you identify which clients are misbehaving?

Tony

-----Original Message-----
From: Brad Knowles [mailto:brad at shub-internet.org] 
Sent: 09 July 2007 17:27
To: Flavin,AJ,Tony,XGH78 R; mayer at gis.net; karen.odonoghue at navy.mil
Cc: ntpwg at lists.ntp.isc.org; stenn at ntp1.ntp.isc.org
Subject: Re: [ntpwg] KISS codes


On 7/9/07, <anthony.flavin at bt.com> wrote:

>  I don't see how this would work. Especially in the case of SNTP. The  
> problem you site is where the sheer number of devices polling the 
> server  swamped it. I believe that at the moment an NTP server only 
> stores the  past 600 which is unlikely to be enough to determine who 
> the trouble  makers are, so unless you are proposing to store the last 
> several thousand  requests, how are you going to determine who to send 
> the codes to?

You solve that problem 600 clients at a time.  You could make the 
cache bigger, but then that just increases the problem of how much 
data you have to store, and how much impact on the server you can see 
from ntpd, and no matter how big you made the cache it would always 
be possible to exceed its size.

So, you cut the problem into chunks, and you solve them as best and 
as quickly as you can.

-- 
Brad Knowles <brad at shub-internet.org>, Consultant & Author LinkedIn
Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks:
<http://tinyurl.com/tj6q4>

09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5938 bytes
Desc: not available
Url : https://lists.ntp.org/pipermail/ntpwg/attachments/20070710/1f7ac556/attachment-0001.bin