[LEAPSECS] [QUAR] Bulletin C and all that

Stephen Scott stephenscott at videotron.ca
Sun Jan 25 15:03:36 EST 2015

Since UTC is defined by the IERS before 1972-01-01 "beginning_of_utc" is not appropriate.
This is the beginning of integer leap seconds, not UTC.
How about "leap_second_epoch" or if the term epoch is undesirable "leap_seconds_origin" labelled as "leap00"


On 2015-01-25 13:11, Rob Seaman wrote:
> Makes sense (and the danger of list processing).  If no further correction I'll shift all the leapNN names to start from June 1972.  Are we all agreed that it is correct to say that the beginning of UTC is 1972-01-01T00:00:00Z with TAI-UTC 10s at that moment?  If so, I'll introduce another name with the same value as the current leap01 but called something like "beginning_of_utc" or some such.
> Thanks!
> Rob
> --
>> On Jan 25, 2015, at 10:00 AM, Michael Deckers via LEAPSECS <leapsecs at leapsecond.com> wrote:
>>   On 2015-01-25 14:58, Rob Seaman wrote:
>>> Please let me know about typos, suggestions, etc.  Needless to say this
>>>   remains a prototype.
>> ...
>>> YYYY MM before  after  encoded crc         IP              Decoded        flags
>>> ------------------------------------------------------------------------------
>>> 1972  1      9     10 f8000a00  f5    -> OK 1972  1  10  1  (1, 0)
>>   It would be incorrect to consider the discontinuity of the difference
>>   TAI - UTC at the epoch when TAI was 1972-01-01T00:00:10 as a leap second;
>>   the difference increased by about 0.108 s, not by 1 s. Hence, a timestamp
>>   such as "1971-12-31T23:59:60.2Z" should not be made acceptable.
>>   The first leap second occurred when UTC reached 1972-07-01; the information
>>   about a leap second says something about TAI - UTC both before and after
>>   the date referenced. At 1972-01-01, however, the information can only say
>>   something about TAI - UTC for TAI on or after 1972-01-01T00:00:10, but
>>   nothing (correct) for smaller values of TAI.
>>   Michael Deckers.
> _______________________________________________
> LEAPSECS mailing list
> LEAPSECS at leapsecond.com
> https://pairlist6.pair.net/mailman/listinfo/leapsecs

This email has been checked for viruses by Avast antivirus software.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/leapsecs/attachments/20150125/437dbb0b/attachment.html>

More information about the LEAPSECS mailing list