Re: [LEAPSECS] Windows Server 2019

2018-07-23 Thread Michael Deckers via LEAPSECS
   On 2018-07-20 18:05, Stephen Scott wrote: 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.     No, they didn't.     A leap second describes a discontinuity in the

Re: [LEAPSECS] Windows Server 2019

2018-07-23 Thread Michael Deckers via LEAPSECS
   On 2018-07-21 01:08, Steve Allen wrote: At that same meeting IAU Comm 31 was led to yield that they had no influence over the leap seconds that the CCIR had instituted, and IAU Comm 31 was pressed to produce a statement declaring that leap seconds were "the optimum solution."

Re: [LEAPSECS] Windows Server 2019

2018-07-23 Thread Steve Allen
On Mon 2018-07-23T13:18:22-0600 Warner Losh hath writ: > In the absence of setting a local time for the leap > second, the offset is controlling and therefore it happens at UTC midnight, > since it's definitely and unambiguously defined in ITU-R TF 460-6 as such > (all known earlier revisions too,

Re: [LEAPSECS] Windows Server 2019

2018-07-23 Thread Warner Losh
On Mon, Jul 23, 2018 at 12:52 PM, Steve Allen wrote: > On Mon 2018-07-23T13:58:49-0400 Stephen Scott hath writ: > > I have not found any specifications or official documents that specify > that > > the leap second shall be incorporated just before the time instant > midnight > > UTC for all UTC

Re: [LEAPSECS] Windows Server 2019

2018-07-23 Thread Steve Allen
On Mon 2018-07-23T13:58:49-0400 Stephen Scott hath writ: > I have not found any specifications or official documents that specify that > the leap second shall be incorporated just before the time instant midnight > UTC for all UTC offset timescales. There is no authority for "all UTC offset

Re: [LEAPSECS] Windows Server 2019

2018-07-23 Thread Stephen Scott
All; What I was trying to get an answer to is "Why is the one leap second treated any different from the other 86400 seconds in the day when offsetting the UTC time to a UTC offset time zone?" Yes, ITU-R TF 460-6 defines the timing of the leap second in UTC. I have not found any

Re: [LEAPSECS] Windows Server 2019

2018-07-23 Thread Warner Losh
On Mon, Jul 23, 2018 at 9:40 AM, Steve Allen wrote: > On Fri 2018-07-20T12:16:07-0600 Warner Losh hath writ: > > 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... > > On Fri 2018-07-20T16:11:12-0400 Stephen Scott hath

Re: [LEAPSECS] Windows Server 2019

2018-07-23 Thread Steve Allen
On Fri 2018-07-20T12:16:07-0600 Warner Losh hath writ: > 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... On Fri 2018-07-20T16:11:12-0400 Stephen Scott hath writ: > What I am asking is WHY. > Where is the standard for that?

Re: [LEAPSECS] Windows Server 2019

2018-07-23 Thread Tony Finch
Stephen Scott wrote: > Where is the standard for that? > Or at least some document that specifies that? The standard for leap seconds is ITU-R TF.460 https://www.itu.int/rec/R-REC-TF.460/en Tony. -- f.anthony.n.finchhttp://dotat.at/ disperse power, foster diversity, and nurture