[LEAPSECS] Windows Server 2019

[Stephen Scott]

On 2018-07-20 14:16, Warner Losh wrote:
>
>
> On Fri, Jul 20, 2018, 12:05 PM Stephen Scott 
> <stephenscott at videotron.ca <mailto:stephenscott at videotron.ca>> wrote:
>
>     I would agree and I am not a fan of leap second smearing.
>     A.)  For an application that depends on an accurate frequency
>     reference smearing over 24 hours represents about a 11 ppm
>     frequency shift. This exceeds the tolerance specified for some
>     audio/video applications.
>     B.) It is not standardized, so maybe it is a smear of maybe its not.
>
>     There is a lack of standards and that is probably the biggest
>     source of most leap second problems.
>
>     I have been searching for standards, documentation on how leap
>     seconds must be applied in local jurisdictions.
>
>     I find it strange that for time in local time zones the time
>     points are shifted by the UTC offset for all 86400 seconds of the day.
>     But that the one leap second is treated differently and is not
>     shifted by the UTC offset.
>     The consequence is that the leap second is being incorporated at
>     critical times of the day in many time zones.
>
>     While there is no perfect answer, it seems that Microsoft Azure
>     servers got it right for the last one, incorporating the leap
>     second just before midnight local time.
>
>
> Unless you are at UTC+0, I don't see how this can be right... Leap 
> seconds happen during the day for most time zones...
What I am asking is WHY.
Where is the standard for that?
Or at least some document that specifies that?

Stephen
>
> Warner
>
>     Control, on Time and in Sync
>     Stephen Scott
>
>
>
>     On 2018-07-20 08:03, Nero Imhard wrote:
>>
>>     scs+ls at eskimo.com <mailto:scs+ls at eskimo.com> schreef op
>>     2018-07-20 11:35:
>>
>>>     The question of what happens if you try to run a leapsec-aware
>>>     kernel downstream of a smearing NTP server is an interesting one.
>>>     My preferred answer is "Don't do that."
>>     If that translates to "don't smear ntp" I could not agree more.
>>     Smearing is catering to those who won't clean up their act,
>>     causing trouble for those who try to do the right thing.
>>     N
>>
>>
>>     _______________________________________________
>>     LEAPSECS mailing list
>>     LEAPSECS at leapsecond.com <mailto:LEAPSECS at leapsecond.com>
>>     https://pairlist6.pair.net/mailman/listinfo/leapsecs
>
>
>     <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>     	Virus-free. www.avast.com
>     <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>
>
>     <#m_-5058450252262385288_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>     _______________________________________________
>     LEAPSECS mailing list
>     LEAPSECS at leapsecond.com <mailto:LEAPSECS at leapsecond.com>
>     https://pairlist6.pair.net/mailman/listinfo/leapsecs
>



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/leapsecs/attachments/20180720/965c6b8b/attachment.html>