>>> Steven Sommars <[email protected]> schrieb am 17.06.2018 um 03:21 in Nachricht <CAD4huA6X81=h4zt+dfenv66ck62gbgrupusnk6j+n_cgn+n...@mail.gmail.com>: > What is the utility of this draft RFC?
If it has no other purpose than helping to understand how ntpq works, it is reason enough IMHO. Another valid purpose is when you do your own monitoring avoiding to call ntpq, just to parse ist output. > 1) The interface is not well defined. Free form ASCII is a poor choice for > interoperability. These are two different issues. > Example: I filed a bug report with the reference ntpd, Bug 3484, for a > specific ntpq - ntpd interop problem and learned that > the draft RFC didn't specify how to encode a null. > 2) Some widespread NTP implementations, e.g., chrony, do not support mode 6. How do you remotely monitor chrony? > 3) Many public NTP servers block mode 6 commands. A few years ago a large > number of public servers under 20% responded to mode 6. See also section 6 > of this draft Many servers today also block FTP, but still it's interesting to know how it works. > 4) Cleaning up the draft may take substantial effort. Is a new > implementation based on this document likely? I think the intentions are to document what is there now (and if bugs are found, maybe correct them). A better implementation is really desireable, but not the intention of the RFC. > 5) Appendix B of RFC1305 seems adequate as a historical note. It does not implement the NTPv4 mode 6 protocol, and it does not document the complete history of the protocol. Regards, Ulrich > > > > > Steven Sommars > > > > On Wed, Jun 13, 2018 at 4:46 AM, Karen O'Donoghue <[email protected]> > wrote: > >> Folks, >> >> Please respond to this WGLC. The deadline is Friday! >> >> Karen >> >> > On May 31, 2018, at 5:26 AM, Karen O'Donoghue <[email protected]> >> wrote: >> > >> > Folks, >> > >> > This begins a 2 week working group last call for the following document: >> > >> > Control Messages Protocol for Use with Network Time Protocol Version 4 >> > https://datatracker.ietf.org/doc/draft-ietf-ntp-mode-6-cmds/ >> > >> > Please review the referenced document and send any comments to the >> mailing list including your assessment of whether this document is mature >> enough to proceed to the IESG. Please note that these messages of support >> for progression to the mailing list will be used to determine WG consensus >> to proceed. >> > >> > Please send all comments in by Friday 15 June 2018. >> > >> > Thank you! >> > Karen and Dieter >> > >> > >> >> _______________________________________________ >> ntp mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/ntp >> _______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
