[HN Gopher] UT1 NTP Time Dissemination
___________________________________________________________________
UT1 NTP Time Dissemination
Author : wglb
Score : 29 points
Date : 2022-01-14 02:32 UTC (20 hours ago)
(HTM) web link (www.nist.gov)
(TXT) w3m dump (www.nist.gov)
| contravariant wrote:
| How bad an idea would it be to just use UT1 everywhere and forget
| about leap seconds?
|
| It'd probably break something but I can't for the life of me
| figure out what.
| LeoPanthera wrote:
| It would be quite bad.
|
| See this page: https://www.ucolick.org/~sla/leapsecs/dutc.html
|
| And scroll down to "Implementing the plan outlined at Torino",
| taking note of the "Notable event" column.
|
| Edit: I think I misunderstood your question. This table shows
| the results of what would happen if we just stopped adding leap
| seconds.
| phaker wrote:
| TAI is the 'UTC without leap seconds'.
|
| UT1 is an evolution of solar time, and wobbles when Earth does
| because it's using the Earth and Sun (and other bodies) as a
| clock.
|
| UTC is TAI with leap seconds added when UT1 drifts too far
| away.
| LeoPanthera wrote:
| "UT1R" is a smoothed version of UT1 with the wobble removed.
| jws wrote:
| I wrote an OS that used TAI as it's time. All in all I was
| pleased with the outcome. UTC conversion happened at parsing
| and formatting, but those are relatively uncommon compared to
| comparison and interval addition so it works well performance
| wise.
| toast0 wrote:
| > The reply will have no special indication that the transmitted
| time is UT1 and not UTC.
|
| And this is how really terrible time situations occur.
| amluto wrote:
| Like when Google's smeared leap second leaked into the general
| NTP pool?
| encoderer wrote:
| Wait what?
| snypher wrote:
| https://developers.google.com/time/smear
___________________________________________________________________
(page generated 2022-01-14 23:01 UTC)