[LEAPSECS] Implementation for |UTC-UT1| > 1 s

[GERRY ASHTON]

> On March 20, 2018 at 3:07 PM Warner Losh <imp at bsdimp.com> wrote:
> 
> 
> On Tue, Mar 20, 2018 at 7:59 AM, GERRY ASHTON <ashtongj at comcast.net> wrote:
> 
> > Perhaps this is too obvious to mention, but if there is a desire to allow
> > |UTC-UT1| somewhat greater than 1 s, but much less than 1 minute, in order
> > to schedule leap seconds further in advance, it will still be necessary to
> > limit each correction to 1 s. This is because a vast number of standards do
> > not allow the number of the second to reach 61.
> >
> 
> I don't see how that follows. The number of seconds in a minute is an
> orthogonal problem ti DUT1, unless you are proposing multiple leap seconds
> at once...
> 
> Warner
> _______________________________________________
> LEAPSECS mailing list
> LEAPSECS at leapsecond.com
> https://pairlist6.pair.net/mailman/listinfo/leapsecs

Exactly. It would break lots of stuff if, for example, two leap seconds were inserted at the end of December 2022. If there was a desire to predict leap seconds a full year in advance, and as of mid-December 2021, it appeared there would be a DUT of 1.9 s in December 2022, it would be necessary to schedule one leap second at the end of December 2022, and another at the end of June 2023.