On Feb 25, 2008, at 7:11 PM, William Herrin wrote:
If the NTP client regularly communicated with the server, this wouldn't be a problem. It would see high jitter on the initial attempt which would settle right down. But NTP is a well behaved protocol. When the server is responding well and it's in sync, NTP backs off to where it sends only a single query every thousand seconds or so. That's more than enough time for the ITR to expire and remove the cached ETR entry so that on the next attempt NTP sees: jitter.
What this simply requires is that the cache be large enough to hold 18 minutes worth of correspondents. This does NOT seem impossible by any means.
Alternately, the scheme could have an application aware cache. Ugly, but not impossible.
Tony -- to unsubscribe send a message to rrg-request@psg.com with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg