3c3
< # a comment, which continues from that symbol until
---
> # a comment, which continues from that symbol until
6,7c6,7
< # There are also special comment lines defined below.
< # A special comment will always have a non-whitespace
---
> # There are also special comment lines defined below.
> # A special comment will always have a non-whitespace
18,23c18,28
< # since 1900.0 and the second column shows the number of
< # seconds that must be added to UTC to compute TAI for
< # any timestamp at or after that epoch. The value on
< # each line is valid from the indicated initial instant
< # until the epoch given on the next one or indefinitely
< # into the future if there is no next line.
---
> # since 1 January 1900, 00:00:00 (1900.0 is also used to
> # indicate the same epoch.) Both of these time stamp formats
> # ignore the complexities of the time scales that were
> # used before the current definition of UTC at the start
> # of 1972. (See note 3 below.)
> # The second column shows the number of seconds that
> # must be added to UTC to compute TAI for any timestamp
> # at or after that epoch. The value on each line is
> # valid from the indicated initial instant until the
> # epoch given on the next one or indefinitely into the
> # future if there is no next line.
25c30
< # the corresponding initial epoch in the usual
---
> # the corresponding initial epoch in the usual
28c33
< #
---
> #
36c41
< # 2. The UTC time scale is realized by many national
---
> # 2. The UTC time scale is realized by many national
47,50c52,55
< # 3. The current defintion of the relationship between UTC
< # and TAI dates from 1 January 1972. A number of different
< # time scales were in use before than epoch, and it can be
< # quite difficult to compute precise timestamps and time
---
> # 3. The current definition of the relationship between UTC
> # and TAI dates from 1 January 1972. A number of different
> # time scales were in use before that epoch, and it can be
> # quite difficult to compute precise timestamps and time
61,63c66,70
< # 4. The insertion of leap seconds into UTC is currently the
< # responsibility of the International Earth Rotation Service,
< # which is located at the Paris Observatory:
---
> # 4. The decision to insert a leap second into UTC is currently
> # the responsibility of the International Earth Rotation and
> # Reference Systems Service. (The name was changed from the
> # International Earth Rotation Service, but the acronym IERS
> # is still used.)
65,67c72
< # Central Bureau of IERS
< # 61, Avenue de l'Observatoire
< # 75014 Paris, France.
---
> # Leap seconds are announced by the IERS in its Bulletin C.
69c74
< # Leap seconds are announced by the IERS in its Bulletin C
---
> # See www.iers.org for more details.
71c76,78
< # See hpiers.obspm.fr or www.iers.org for more details.
---
> # Every national laboratory and timing center uses the
> # data from the BIPM and the IERS to construct UTC(lab),
> # their local realization of UTC.
73,76d79
< # All national laboratories and timing centers use the
< # data from the BIPM and the IERS to construct their
< # local realizations of UTC.
< #
78,79c81,82
< # of dropping seconds ("negative" leap seconds), this has
< # never been done and is unlikely to be necessary in the
---
> # of dropping seconds ("negative" leap seconds), this has
> # never been done and is unlikely to be necessary in the
85,90c88,93
< # leap second is not well defined. The official name of that leap
< # second is 23:59:60, but there is no way of representing that time
< # in these systems.
< # Many systems of this type effectively stop the system clock for
< # one second during the leap second and use a time that is equivalent
< # to 23:59:59 UTC twice. For these systems, the corresponding TAI
---
> # leap second is not well defined. The official name of that leap
> # second is 23:59:60, but there is no way of representing that time
> # in these systems.
> # Many systems of this type effectively stop the system clock for
> # one second during the leap second and use a time that is equivalent
> # to 23:59:59 UTC twice. For these systems, the corresponding TAI
105c108
< # in the table must occur the second time that a time equivlent to
---
> # in the table must occur the second time that a time equivalent to
115c118,121
< # time scale with no discontinuity in the time interval.
---
> # time scale with no discontinuity in the time interval. However,
> # although the long-term behavior of the time scale is correct in both
> # methods, the second method is technically not correct because it adds
> # the extra second to the wrong day.
117,121c123,127
< # This complexity would not be needed for negative leap seconds (if they
< # are ever used). The UTC time would skip 23:59:59 and advance from
< # 23:59:58 to 00:00:00 in that case. The TAI offset would decrease by
< # 1 second at the same instant. This is a much easier situation to deal
< # with, since the difficulty of unambiguously representing the epoch
---
> # This complexity would not be needed for negative leap seconds (if they
> # are ever used). The UTC time would skip 23:59:59 and advance from
> # 23:59:58 to 00:00:00 in that case. The TAI offset would decrease by
> # 1 second at the same instant. This is a much easier situation to deal
> # with, since the difficulty of unambiguously representing the epoch
129c135
< # jlevine@boulder.nist.gov
---
> # Judah.Levine@nist.gov
133c139
< # The following line shows this last update date in NTP timestamp
---
> # The following line shows this last update date in NTP timestamp
136c142
< # be identified by the unique pair of characters in the first two
---
> # be identified by the unique pair of characters in the first two
142,143c148,149
< # which is 1900.0. The Modified Julian Day number corresponding
< # to the NTP time stamp, X, can be computed as
---
> # which is 1 January 1900, 00:00:00. The Modified Julian Day number
> # corresponding to the NTP time stamp, X, can be computed as
147,153c153,160
< # where the first term converts seconds to days and the second
< # term adds the MJD corresponding to 1900.0. The integer portion
< # of the result is the integer MJD for that day, and any remainder
< # is the time of day, expressed as the fraction of the day since 0
< # hours UTC. The conversion from day fraction to seconds or to
< # hours, minutes, and seconds may involve rounding or truncation,
< # depending on the method used in the computation.
---
> # where the first term converts seconds to days and the second
> # term adds the MJD corresponding to the time origin defined above.
> # The integer portion of the result is the integer MJD for that
> # day, and any remainder is the time of day, expressed as the
> # fraction of the day since 0 hours UTC. The conversion from day
> # fraction to seconds or to hours, minutes, and seconds may involve
> # rounding or truncation, depending on the method used in the
> # computation.
155c162
< # The data in this file will be updated periodically as new leap
---
> # The data in this file will be updated periodically as new leap
157c164
< # above, the update time (in NTP format) will be added to the basic
---
> # above, the update time (in NTP format) will be added to the basic
159c166
< # In addition, the generic name leap-seconds.list will always point to
---
> # In addition, the generic name leap-seconds.list will always point to
163c170
< # is announced.
---
> # is announced.
166,170c173,178
< # in this file in units of seconds since 1900.0. This expiration date
< # will be changed at least twice per year whether or not a new leap
< # second is announced. These semi-annual changes will be made no
< # later than 1 June and 1 December of each year to indicate what
< # action (if any) is to be taken on 30 June and 31 December,
---
> # in this file in units of seconds since the origin at the instant
> # 1 January 1900, 00:00:00. This expiration date will be changed
> # at least twice per year whether or not a new leap second is
> # announced. These semi-annual changes will be made no later
> # than 1 June and 1 December of each year to indicate what
> # action (if any) is to be taken on 30 June and 31 December,
174c182
< # In the unlikely event that a leap second is announced with an
---
> # In the unlikely event that a leap second is announced with an
178,180c186,188
< # (whichever is later).
< # If an announcement by the IERS specifies that no leap second is
< # scheduled, then only the expiration date of the file will
---
> # (whichever is later).
> # If an announcement by the IERS specifies that no leap second is
> # scheduled, then only the expiration date of the file will
182c190
< # current -- the update time stamp, the data and the name of the file
---
> # current -- the update time stamp, the data and the name of the file
185,186c193,194
< # Updated through IERS Bulletin C46
< # File expires on: 28 June 2014
---
> # Updated through IERS Bulletin C48
> # File expires on: 28 June 2015
188c196
< #@ 3612902400
---
> #@ 3644438400
225c233
< # of both the last modification time and the
---
> # of both the last modification time and the
231c239
< #h 1151a8f e85a5069 9000fcdb 3d5e5365 1d505b37
---
> #h a4862ccd c6f43c6 964f3604 85944a26 b5cfad4e
< # a comment, which continues from that symbol until
---
> # a comment, which continues from that symbol until
6,7c6,7
< # There are also special comment lines defined below.
< # A special comment will always have a non-whitespace
---
> # There are also special comment lines defined below.
> # A special comment will always have a non-whitespace
18,23c18,28
< # since 1900.0 and the second column shows the number of
< # seconds that must be added to UTC to compute TAI for
< # any timestamp at or after that epoch. The value on
< # each line is valid from the indicated initial instant
< # until the epoch given on the next one or indefinitely
< # into the future if there is no next line.
---
> # since 1 January 1900, 00:00:00 (1900.0 is also used to
> # indicate the same epoch.) Both of these time stamp formats
> # ignore the complexities of the time scales that were
> # used before the current definition of UTC at the start
> # of 1972. (See note 3 below.)
> # The second column shows the number of seconds that
> # must be added to UTC to compute TAI for any timestamp
> # at or after that epoch. The value on each line is
> # valid from the indicated initial instant until the
> # epoch given on the next one or indefinitely into the
> # future if there is no next line.
25c30
< # the corresponding initial epoch in the usual
---
> # the corresponding initial epoch in the usual
28c33
< #
---
> #
36c41
< # 2. The UTC time scale is realized by many national
---
> # 2. The UTC time scale is realized by many national
47,50c52,55
< # 3. The current defintion of the relationship between UTC
< # and TAI dates from 1 January 1972. A number of different
< # time scales were in use before than epoch, and it can be
< # quite difficult to compute precise timestamps and time
---
> # 3. The current definition of the relationship between UTC
> # and TAI dates from 1 January 1972. A number of different
> # time scales were in use before that epoch, and it can be
> # quite difficult to compute precise timestamps and time
61,63c66,70
< # 4. The insertion of leap seconds into UTC is currently the
< # responsibility of the International Earth Rotation Service,
< # which is located at the Paris Observatory:
---
> # 4. The decision to insert a leap second into UTC is currently
> # the responsibility of the International Earth Rotation and
> # Reference Systems Service. (The name was changed from the
> # International Earth Rotation Service, but the acronym IERS
> # is still used.)
65,67c72
< # Central Bureau of IERS
< # 61, Avenue de l'Observatoire
< # 75014 Paris, France.
---
> # Leap seconds are announced by the IERS in its Bulletin C.
69c74
< # Leap seconds are announced by the IERS in its Bulletin C
---
> # See www.iers.org for more details.
71c76,78
< # See hpiers.obspm.fr or www.iers.org for more details.
---
> # Every national laboratory and timing center uses the
> # data from the BIPM and the IERS to construct UTC(lab),
> # their local realization of UTC.
73,76d79
< # All national laboratories and timing centers use the
< # data from the BIPM and the IERS to construct their
< # local realizations of UTC.
< #
78,79c81,82
< # of dropping seconds ("negative" leap seconds), this has
< # never been done and is unlikely to be necessary in the
---
> # of dropping seconds ("negative" leap seconds), this has
> # never been done and is unlikely to be necessary in the
85,90c88,93
< # leap second is not well defined. The official name of that leap
< # second is 23:59:60, but there is no way of representing that time
< # in these systems.
< # Many systems of this type effectively stop the system clock for
< # one second during the leap second and use a time that is equivalent
< # to 23:59:59 UTC twice. For these systems, the corresponding TAI
---
> # leap second is not well defined. The official name of that leap
> # second is 23:59:60, but there is no way of representing that time
> # in these systems.
> # Many systems of this type effectively stop the system clock for
> # one second during the leap second and use a time that is equivalent
> # to 23:59:59 UTC twice. For these systems, the corresponding TAI
105c108
< # in the table must occur the second time that a time equivlent to
---
> # in the table must occur the second time that a time equivalent to
115c118,121
< # time scale with no discontinuity in the time interval.
---
> # time scale with no discontinuity in the time interval. However,
> # although the long-term behavior of the time scale is correct in both
> # methods, the second method is technically not correct because it adds
> # the extra second to the wrong day.
117,121c123,127
< # This complexity would not be needed for negative leap seconds (if they
< # are ever used). The UTC time would skip 23:59:59 and advance from
< # 23:59:58 to 00:00:00 in that case. The TAI offset would decrease by
< # 1 second at the same instant. This is a much easier situation to deal
< # with, since the difficulty of unambiguously representing the epoch
---
> # This complexity would not be needed for negative leap seconds (if they
> # are ever used). The UTC time would skip 23:59:59 and advance from
> # 23:59:58 to 00:00:00 in that case. The TAI offset would decrease by
> # 1 second at the same instant. This is a much easier situation to deal
> # with, since the difficulty of unambiguously representing the epoch
129c135
< # jlevine@boulder.nist.gov
---
> # Judah.Levine@nist.gov
133c139
< # The following line shows this last update date in NTP timestamp
---
> # The following line shows this last update date in NTP timestamp
136c142
< # be identified by the unique pair of characters in the first two
---
> # be identified by the unique pair of characters in the first two
142,143c148,149
< # which is 1900.0. The Modified Julian Day number corresponding
< # to the NTP time stamp, X, can be computed as
---
> # which is 1 January 1900, 00:00:00. The Modified Julian Day number
> # corresponding to the NTP time stamp, X, can be computed as
147,153c153,160
< # where the first term converts seconds to days and the second
< # term adds the MJD corresponding to 1900.0. The integer portion
< # of the result is the integer MJD for that day, and any remainder
< # is the time of day, expressed as the fraction of the day since 0
< # hours UTC. The conversion from day fraction to seconds or to
< # hours, minutes, and seconds may involve rounding or truncation,
< # depending on the method used in the computation.
---
> # where the first term converts seconds to days and the second
> # term adds the MJD corresponding to the time origin defined above.
> # The integer portion of the result is the integer MJD for that
> # day, and any remainder is the time of day, expressed as the
> # fraction of the day since 0 hours UTC. The conversion from day
> # fraction to seconds or to hours, minutes, and seconds may involve
> # rounding or truncation, depending on the method used in the
> # computation.
155c162
< # The data in this file will be updated periodically as new leap
---
> # The data in this file will be updated periodically as new leap
157c164
< # above, the update time (in NTP format) will be added to the basic
---
> # above, the update time (in NTP format) will be added to the basic
159c166
< # In addition, the generic name leap-seconds.list will always point to
---
> # In addition, the generic name leap-seconds.list will always point to
163c170
< # is announced.
---
> # is announced.
166,170c173,178
< # in this file in units of seconds since 1900.0. This expiration date
< # will be changed at least twice per year whether or not a new leap
< # second is announced. These semi-annual changes will be made no
< # later than 1 June and 1 December of each year to indicate what
< # action (if any) is to be taken on 30 June and 31 December,
---
> # in this file in units of seconds since the origin at the instant
> # 1 January 1900, 00:00:00. This expiration date will be changed
> # at least twice per year whether or not a new leap second is
> # announced. These semi-annual changes will be made no later
> # than 1 June and 1 December of each year to indicate what
> # action (if any) is to be taken on 30 June and 31 December,
174c182
< # In the unlikely event that a leap second is announced with an
---
> # In the unlikely event that a leap second is announced with an
178,180c186,188
< # (whichever is later).
< # If an announcement by the IERS specifies that no leap second is
< # scheduled, then only the expiration date of the file will
---
> # (whichever is later).
> # If an announcement by the IERS specifies that no leap second is
> # scheduled, then only the expiration date of the file will
182c190
< # current -- the update time stamp, the data and the name of the file
---
> # current -- the update time stamp, the data and the name of the file
185,186c193,194
< # Updated through IERS Bulletin C46
< # File expires on: 28 June 2014
---
> # Updated through IERS Bulletin C48
> # File expires on: 28 June 2015
188c196
< #@ 3612902400
---
> #@ 3644438400
225c233
< # of both the last modification time and the
---
> # of both the last modification time and the
231c239
< #h 1151a8f e85a5069 9000fcdb 3d5e5365 1d505b37
---
> #h a4862ccd c6f43c6 964f3604 85944a26 b5cfad4e