On 1/26/2009 8:30 AM, David Malone wrote: > "David E. Ross" <[email protected]> writes: > >> Per my earlier reply, they should be set only during the same day that >> ends with a leap-second. > > Note that while some of the current RFCs say "current day" the draft > of the NTPv4 spec at: > > http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-proto-11.txt > > says "end of the current month". I guess this is to bring the spec > inline with existing practice. > > David.
Whether the leap-second flag means "end of the current day" (per RFCs 1305 and 4330) or "end of the current month" (per the draft RFC for NTP v.4), indicating a leap-second today is an error. When such an error is seen, it makes me question the accuracy of the affected NTP server. After all, if they can't get the leap-second flag correct (something I dealt with in the early 1970s before there was NTP), what else are they doing wrong? By the way, the draft RFC expires in a little over a month from now. -- David E. Ross <http://www.rossde.com/>. Don't ask "Why is there road rage?" Instead, ask "Why NOT Road Rage?" or "Why Is There No Such Thing as Fast Enough?" <http://www.rossde.com/roadrage.html> _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
