[Ntp] Antw: Re: Leap second draft

>>> Martin Burnicki <martin.burnicki@meinberg.de> schrieb am 24.01.2020 um
16:09 in
Nachricht <d28630bc-6f3c-79d7-819d-484666cf8290@meinberg.de>:

...
> This is one of the reasons why ntpd sends leap bits "unsynchronized" for
> a short time around the leap second. This doesn't hurt or confuse the
> client.

Given the typical polling intervals that UNSYNC status may be valid
significantly longer than the actual leap second. That is why I think it's
wrong to set UNSYNC during leap second. It's also against expectations: Why
should an NTP server that is stable be UNSYNC or jump to stratum 16 suddenly?

This simply feels wrong.

Regards,
Ulrich

> 
> Martin
> -- 
> Martin Burnicki
> 
> Senior Software Engineer
> 
> MEINBERG Funkuhren GmbH & Co. KG
> Email: martin.burnicki@meinberg.de 
> Phone: +49 5281 9309-414
> Linkedin: https://www.linkedin.com/in/martinburnicki/ 
> 
> Lange Wand 9, 31812 Bad Pyrmont, Germany
> Amtsgericht Hannover 17HRA 100322
> Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg,
> Andre Hartmann, Heiko Gerstung
> Websites: https://www.meinberg.de  https://www.meinbergglobal.com 
> Training: https://www.meinberg.academy 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp 