[ntp:questions] Re: Contradicting RFC<---> Implementation

Richard B. Gilbert rgilbert88 at comcast.net
Mon Oct 3 19:16:09 UTC 2005

Remo wrote:

>The NTP RFC does'nt mention anything explicitly about the sanity checks
>of the clock_select procedure, but the rootdispersion check for an
>association is made with the MAXDISPERSE(16 sec).{according to RFC}.
>In some implementations, I could see that the limit is MAXDISTANCE + 2
>(which is 3 seconds). In the time, wondering about this change and the
>"3 seconds", I found that the w32time service provides a rootdispersion
>above 1 second.
>Could anyone let me know the reason for this change and why the w32time
>service is way above threshold of 1 sec???
>Thanks for your time!!!
W32Time is a Microsoft implementation of the SNTP protocol.  It does not 
comply with the RFC for SNTP.   Questions and complaints should be 
directed to Microsoft!   (lots of luck!!)

More information about the questions mailing list