[ntpwg] Re: [ntp:hackers] Re: peer flash bits
David L. Mills
mills at udel.edu
Sun Mar 13 14:47:49 UTC 2005
The ntpd doesn't return anything except raw status bits and raw
vegetables. It does no interpret the bits or provide flash tool tips.
That's the function of ntpq in whatever form. See the control and
monitoring protocol in the appendix to rfc1305. That extends to the
traps, status bits and other data defined in that appendix. The NTPv4
spec is unchanged from the NTPv3 spec in that area, at least for the
present. The present might morph with no apology.
Can we go beyond the flasher issue, which is not a specification issue?
Can we get on with the spec itself? Has anybody looked at the
flowcharts? Are there comments on the weekly reports I have made to the
hackers group? Has anybody comment on the test suite draft? Has anybody
comment on the algorithms, protocol and architecture? Is there any
progress on the Autokey specification?
Harlan Stenn wrote:
>That works for me. I'll get on it, thanks!.
>I'm also ready to have ntpd return:
> status=(syspeer,15 events,reach),
>and similarly the flash value, mostly so this situation will never happen
More information about the ntpwg