Re: [Ntp] Antw: [EXT] Re: Timescales

[Ulrich Windl <[e-mail]>]

>>> Miroslav Lichvar <[e-mail]> schrieb am 09.12.2020 um 14:46 in
Nachricht <20201209134612.GC2352378@localhost>:
> On Wed, Dec 09, 2020 at 02:29:32PM +0100, Ulrich Windl wrote:
>> However you could see the leap indication flag also as "leap confirmation"
>> flag (actually there will be a leap event). With only DCF‑77 clocks this 
> could
>> be a problem. As said earlier, it would be best if NTP could reliably 
> transfer
>> the leapsecond table, or at least the relevant part of it to make clients 
> know
>> in advance that and when a leap event is scheduled.
> 
> There is the tzdist (RFC7808) protocol designed for that.
> 
> NTP could distribute a leap‑second table (it already did it with
> Autokey, right?), but isn't NTP about distributing current time,
> rather than reconstructing time in the past or future?

Hi!

You all seem to have missed my point: In the recent past there was a lot of
discussion and confusion what the LI (Leap Indicator) means:
Leap second today, leap second at the end of the month, leap second soon. So
having the definite time of the next leap event would all make this easier.
Actually it could make the LI even obsolete.

Regards,
Ulrich

> 
> ‑‑ 
> Miroslav Lichvar