Opened 8 years ago

Closed 8 years ago

#31 closed defect (fixed)

Include leap seconds?

Reported by: martin.burnicki@… Owned by: cyrus@…
Priority: major Milestone:
Component: service Version:
Severity: - Keywords:
Cc:

Description

If you are going to work with historical data it might be important to know at which points in time leap seconds have been inserted into the UTC time scale, so it would be very helpful if the tzdist protocol would provide a way to distribute a list of leap seconds as provided by the NIST leap second file, or the leap second file included in the TZ data base.

Nowadays the NTP protocol is mostly used to synchronize time between computers and other devices. However, there's also the new Precision Time Protocol (PTP, IEEE 1588) which uses time stamps based on TAI, and is used more and more in new applications.

If you want to relate TAI to UTC at a given (current, or past) time you need to know *when* a leap second will be, or has been inserted in the UTC time scale.

So if this information could also be distributed via the tzdist protocol this would be very helpful for future interaction of systems based on TAI and UTC.

Change History (2)

comment:1 Changed 8 years ago by lear@…

Nice work done by Ken with proof of concept with a pseudo-timezone. Question remains whether to codify this in some way. Discussion to occur on list. People to get their views out onto list by the 9th of January.

Should we have considerations for leap seconds in the document?
Should we handle leap second with a pseudo timezone or some other way?

Maybe not /zones/etc/TAI but /leapsecond.

We need a proposal.
Ken has done a JSON representation

comment:2 Changed 8 years ago by mglt.ietf@…

  • Resolution set to fixed
  • Status changed from new to closed

leap seconds have been addressed (see section 5.6 of draft version 05) with an additional action

Note: See TracTickets for help on using tickets.