Leap second

Screen grab of the UTC clock from www.time.gov during the leap second on June 30, 2015.

A leap second is a one-second adjustment that is occasionally applied to Coordinated Universal Time (UTC) in order to keep its time of day close to the mean solar time, or UT1. Without such a correction, time reckoned by Earth's rotation drifts away from atomic time because of irregularities in the Earth's rate of rotation. Since this system of correction was implemented in 1972, 26 leap seconds have been inserted, the most recent on June 30, 2015 at 23:59:60 UTC.[1]

The UTC time standard, which is widely used for international timekeeping and as the reference for civil time in most countries, uses the international system (SI) definition of the second, based on atomic clocks. Like most time standards, UTC defines a grouping of seconds into minutes, hours, days, months, and years. However, the duration of one mean solar day is now slightly longer than 24 hours (86400 SI seconds) because the rotation of the Earth has slowed down. Therefore, if the UTC day were defined as precisely 86400 SI seconds, the UTC time-of-day would slowly drift apart from that of solar-based standards, such as Greenwich Mean Time (GMT) and its successor UT1. The purpose of a leap second is to compensate for this drift, by occasionally scheduling some UTC days with 86401 or (in principle) 86399 SI seconds.

Specifically, a positive leap second is inserted between second 23:59:59 of a chosen UTC calendar date (the last day of a month, usually June 30 or December 31) and second 00:00:00 of the following date. This extra second is displayed on UTC clocks as 23:59:60. On clocks that display local time tied to UTC, the leap second may be inserted at the end of some other hour (or half-hour or quarter-hour), depending on the local time zone. A negative leap second would suppress second 23:59:59 of the last day of a chosen month, so that second 23:59:58 of that date would be followed immediately by second 00:00:00 of the following date. However, negative leap seconds have never been needed since the UTC standard was established, and are highly unlikely to ever be.

Because the Earth's rotation speed varies in response to climatic and geological events, UTC leap seconds are irregularly spaced and unpredictable. Insertion of each UTC leap second is usually decided about six months in advance by the International Earth Rotation and Reference Systems Service (IERS), when needed to ensure that the difference between the UTC and UT1 readings will never exceed 0.9 seconds. 26 positive leap seconds have been scheduled so far.[1][2]

History

Graph showing the difference between UT1 and UTC. Vertical segments correspond to leap seconds.

About 140 AD, Ptolemy, the Alexandrian astronomer, sexagesimally subdivided both the mean solar day and the true solar day to at least six places after the sexagesimal point, and he used simple fractions of both the equinoctial hour and the seasonal hour, none of which resemble the modern second.[3] Muslim scholars, including al-Biruni in 1000, subdivided the mean solar day into 24 equinoctial hours, each of which was subdivided sexagesimally, that is into the units of minute, second, third, fourth and fifth, creating the modern second as 1⁄60 of 1⁄60 of 1⁄24 = 1⁄86400 of the mean solar day in the process.[4] With this definition, the second was proposed in 1874 as the base unit of time in the CGS system of units.[5] Soon afterwards Simon Newcomb and others discovered that Earth's rotation period varied irregularly,[6] so in 1952, the International Astronomical Union (IAU) defined the second as a fraction of the sidereal year. Because the tropical year was considered more fundamental than the sidereal year, in 1955, the IAU redefined the second as the fraction 1⁄31,556,925.9747 of the 1900.0 mean tropical year, which was adopted in 1956 by the International Committee for Weights and Measures and in 1960 by the General Conference on Weights and Measures, becoming a part of the International System of Units (SI).[7]

Eventually, this definition too was found to be inadequate for precise time measurements, so in 1967, the SI second was again redefined as 9,192,631,770 periods of the radiation emitted by a caesium-133 atom in the transition between the two hyperfine levels of its ground state.[8] That value agreed to 1 part in 1010 with the astronomical (ephemeris) second then in use.[9] It was also close to 1⁄86400 of the mean solar day as averaged between years 1750 and 1892.

However, for the past several centuries, the length of the mean solar day has been increasing by about 1.4–1.7 ms per century, depending on the averaging time.[10][11][12] By 1961, the mean solar day was already a millisecond or two longer than 86,400 SI seconds.[13] Therefore, time standards that change the date after precisely 86,400 SI seconds, such as the International Atomic Time (TAI), will get increasingly ahead of time standards tied to the mean solar day, such as Greenwich Mean Time (GMT).

When the Coordinated Universal Time standard was instituted in 1961, based on atomic clocks, it was felt necessary to maintain agreement with the GMT time of day, which, until then, had been the reference for broadcast time services. Thus, from 1961 to 1971, the rate of (some) atomic clocks was constantly slowed to remain synchronised with GMT. During that period, therefore, the "seconds" of broadcast services were actually slightly longer than the SI second and closer to the GMT seconds.

In 1972, the leap-second system was introduced so that the broadcast UTC seconds could be made exactly equal to the standard SI second, while still maintaining the UTC time of day and changes of UTC date synchronized with those of UT1 (the solar time standard that superseded GMT).[8] By then, the UTC clock was already 10 seconds behind TAI, which had been synchronized with UT1 in 1958, but had been counting true SI seconds since then. After 1972, both clocks have been ticking in SI seconds, so the difference between their readouts at any time is 10 seconds plus the total number of leap seconds that have been applied to UTC (36 seconds in July 2015).

Insertion of leap seconds

Announced leap seconds to date
Year Jun 30 Dec 31
1972 +1 +1
1973 0 +1
1974 0 +1
1975 0 +1
1976 0 +1
1977 0 +1
1978 0 +1
1979 0 +1
1980 0 0
1981 +1 0
1982 +1 0
1983 +1 0
1984 0 0
1985 +1 0
1986 0 0
1987 0 +1
1988 0 0
1989 0 +1
1990 0 +1
1991 0 0
1992 +1 0
1993 +1 0
1994 +1 0
1995 0 +1
1996 0 0
1997 +1 0
1998 0 +1
1999 0 0
2000 0 0
2001 0 0
2002 0 0
2003 0 0
2004 0 0
2005 0 +1
2006 0 0
2007 0 0
2008 0 +1
2009 0 0
2010 0 0
2011 0 0
2012 +1 0
2013 0 0
2014 0 0
2015 +1 0
2016 0
Year Jun 30 Dec 31
Total 11 15
26
Current TAI − UTC
36

The scheduling of leap seconds was initially delegated to the Bureau International de l'Heure (BIH), but passed to the International Earth Rotation and Reference Systems Service (IERS) on January 1, 1988. IERS usually decides to apply a leap second whenever the difference between UTC and UT1 approaches 0.6 s, in order to keep the difference between UTC and UT1 from exceeding 0.9 s.

The UTC standard allows leap seconds to be applied at the end of any UTC month, with first preference to June and December and second preference to March and September. As of July 2015, all of them have been inserted either at the end of June 30 or December 31. IERS publishes announcements every six months, whether leap seconds are to occur or not, in its "Bulletin C". Such announcements are typically published well in advance of each possible leap second date – usually in early January for June 30 and in early July for December 31.[14][15] Some time signal broadcasts give voice announcements of an impending leap second.

Between 1972 and 2012, a leap second has been inserted about every 18 months, on average. However, the spacing is quite irregular and apparently increasing: there were no leap seconds in the seven-year interval between January 1, 1999 and December 31, 2005, but there were nine leap seconds in the eight years 1972–1979.

Unlike leap days, UTC leap seconds occur simultaneously worldwide; for example, the leap second on December 31, 2005 23:59:60 UTC was December 31, 2005 18:59:60 (6:59:60 p.m.) in U.S. Eastern Standard Time and January 1, 2006 08:59:60 (a.m.) in Japan Standard Time.

Not all clocks implement leap seconds in the same manner as UTC. Leap seconds in Unix time are commonly implemented by repeating the last second of the day. Network Time Protocol freezes time during the leap second. Other experimental schemes smear time in the vicinity of a leap second.[16]

Slowing rotation of the Earth

Deviation of day length from SI based day, 1962–2014
Main article: ΔT

Leap seconds are irregularly spaced because the Earth's rotation speed changes irregularly. Indeed, the Earth's rotation is quite unpredictable in the long term, which explains why leap seconds are announced only six months in advance.

A mathematical model of the variations in the length of the solar day was developed by F. R. Stephenson and L. V. Morrison,[12] based on records of eclipses for the period 700 BC to 1623 AD, telescopic observations of occultations for the period 1623 until 1967 and atomic clocks thereafter. The model shows a steady increase of the mean solar day by 1.70 ms (± 0.05 ms) per century, plus a periodic shift of about 4 ms amplitude and period of about 1,500 yr.[12] Over the last few centuries, the periodic component reduced the rate of lengthening of the mean solar day to about 1.4 ms per century.[17]

The main reason for the slowing down of the Earth's rotation is tidal friction, which alone would lengthen the day by 2.3 ms/century.[12] Other contributing factors are the movement of the Earth's crust relative to its core, changes in mantle convection, and any other events or processes that cause a significant redistribution of mass. These processes change the Earth's moment of inertia, affecting the rate of rotation due to conservation of angular momentum, sometimes increasing earth's rotational speed (decreasing the solar day and opposing tidal friction). For example, glacial rebound shortens the solar day by 0.6 ms/century and the 2004 Indian Ocean earthquake is thought to have shortened it by 2.68 microseconds.[18] It is evident from the figure that the Earth has actually sped up since the initiation of the current system in 1971, and the rate of leap second insertions has therefore been decreasing.

Proposal to abolish leap seconds

The irregularity and unpredictability of UTC leap seconds is problematic for several areas, especially computing. For example, to compute the elapsed time in seconds between two given UTC past dates requires consulting a table of leap seconds, which needs to be updated whenever a new leap second is announced. Moreover, it is not possible to compute accurate time intervals for UTC dates that are more than about six months in the future.

On July 5, 2005, the Head of the Earth Orientation Center of the IERS sent a notice to IERS Bulletins C and D subscribers, soliciting comments on a U.S. proposal before the ITU-R Study Group 7's WP7-A to eliminate leap seconds from the UTC broadcast standard before 2008 (the ITU-R is responsible for the definition of UTC). [lower-alpha 1] It was expected to be considered in November 2005, but the discussion has since been postponed.[20] Under the proposal, leap seconds would be technically replaced by leap hours as an attempt to satisfy the legal requirements of several ITU-R member nations that civil time be astronomically tied to the Sun.

A number of objections to the proposal have been raised. Dr. P. Kenneth Seidelmann, editor of the Explanatory Supplement to the Astronomical Almanac, wrote a letter[21] lamenting the lack of consistent public information about the proposal and adequate justification. Steve Allen of the University of California, Santa Cruz cited what he claimed to be the large impact on astronomers in a Science News article.[22] He has an extensive online site[23] devoted to the issues and the history of leap seconds, including a set of references about the proposal and arguments against it.[24]

At the 2014 General Assembly of the International Union of Radio Scientists (URSI), Dr. Demetrios Matsakis, the United States Naval Observatory's Chief Scientist for Time Services, presented the reasoning in favor of the redefinition and rebuttals to the arguments made against it.[25] He stressed the practical inability of software programmers to allow for the fact that leap seconds make time appear to go backwards, particularly when most of them do not even know that leap seconds exist. The possibility of leap seconds being a hazard to navigation was presented, as well as the observed effects on commerce.

The United States formulated its position on this matter based upon the advice of the National Telecommunications and Information Administration[26] and the Federal Communications Commission (FCC), which solicited comments from the general public.[27] This position is in favor of the redefinition.[28][lower-alpha 2]

In 2011, Chunhao Han of the Beijing Global Information Center of Application and Exploration said China had not decided what its vote would be in January 2012, but some Chinese scholars consider it important to maintain a link between civil and astronomical time due to Chinese tradition. The 2012 vote was ultimately deferred.[30] At an ITU/BIPM-sponsored workshop on the leap second, Dr. Han expressed his personal view in favor of abolishing the leap second,[31] and similar support for the redefinition was again expressed by Dr. Han, along with other Chinese timekeeping scientists, at the URSI General Assembly in 2014.

At a special session of the Asia-Pacific Telecommunity Meeting on February 10, 2015, Chunhao Han indicated China was now supporting the elimination of future leap seconds, as were all the other presenting national representatives (from Australia, Japan, and the Republic of Korea). At this meeting, Bruce Warrington (NMI, Australia) and Tsukasa Iwama (NICT, Japan) indicated particular concern for the financial markets due to the leap second occurring in the middle of a workday in their part of the world.[lower-alpha 3] Subsequent to the CPM15-2 meeting in March/April 2015 the draft gives four methods which the WRC-15 might use to satisfy Resolution 653 from WRC-12.[34]

Arguments against the proposal include the unknown expense of such a major change and the fact that universal time will no longer correspond to mean solar time. It is also answered that two timescales that do not follow leap seconds are already available, International Atomic Time (TAI) and Global Positioning System (GPS) time. Computers, for example, could use these and convert to UTC or local civil time as necessary for output. Inexpensive GPS timing receivers are readily available, and the satellite broadcasts include the necessary information to convert GPS time to UTC. It is also easy to convert GPS time to TAI, as TAI is always exactly 19 seconds ahead of GPS time. Examples of systems based on GPS time include the CDMA digital cellular systems IS-95 and CDMA2000. In general, computer systems use UTC and synchronize their clocks using Network Time Protocol (NTP). Systems that cannot tolerate disruptions caused by leap seconds can base their time on TAI and use Precision Time Protocol. However, the BIPM has pointed out that this proliferation of timescales leads to confusion.[35]

At the 47th meeting of the Civil Global Positioning System Service Interface Committee in Fort Worth, Texas in September 2007, it was announced that a mailed vote would go out on stopping leap seconds. The plan for the vote was:[36]

In January 2012, rather than decide yes or no per this plan, the ITU decided to postpone a decision on leap seconds to the World Radiocommunication Conference in November 2015. At this conference, it was again decided to continue using leap seconds, pending further study and consideration at the next conference in 2023.[38]

In October 2014, Dr. Wlodzimierz Lewandowski, chair of the timing subcommittee of the Civil GPS Interface Service Committee and a member of the ESA Navigation Program Board, presented a CGSIC-endorsed resolution to the ITU that supported the redefinition and described leap seconds as a "hazard to navigation".[39]

Some of the objections to the proposed change have been answered by its opponents. For example, Dr. Felicitas Arias, who, as Director of the International Bureau of Weights and Measures (BIPM)'s Time, Frequency, and Gravimetry Department, is responsible for generating UTC noted in a press release that the drift of about one minute every 60–90 years could be compared to the 16-minute annual variation between true solar time and mean solar time, the one hour offset by use of daylight time, and the several-hours offset in certain geographically extra-large time zones.[40]

Examples of problems associated with the leap second

A number of organizations reported problems caused by flawed software following the June 30, 2012 leap second. Among the sites which reported problems were reddit (Apache Cassandra), Mozilla (Hadoop),[41] Qantas Airways,[42] and various sites running Linux.[43]

Older versions of Motorola Oncore VP, UT, GT, and M12 GPS receivers had a software bug that would cause a single timestamp to be off by a day if no leap second was scheduled for 256 weeks. On November 28, 2003, this actually happened. At midnight, the receivers with this firmware reported November 29, 2003 for one second and then reverted to November 28, 2003.[44][45]

Older Trimble GPS receivers had a software flaw that would insert a leap second immediately after the GPS constellation started broadcasting the next leap second insertion time (some months in advance of the actual leap second), rather than waiting for the next leap second to happen. This left the receiver's time off by a second in the interim.[46][47]

Older Datum Tymeserv 2100 GPS receivers and Symmetricomm Tymeserv 2100 receivers also have a similar flaw as the previous noted Trimble GPS receivers, where the time is off by one second. The advance announcement of the leap second is applied as soon as the message is received, instead of waiting for the correct date. There is no firmware upgrade for this problem. A workaround has been described and tested, but if the GPS system rebroadcasts the announcement, or the unit is powered off, the issue will occur again.[48]

The NTP packet includes a leap second flag, which informs the user that a leap second is imminent. This, among other things, allows the user to distinguish between a bad measurement that should be ignored and a genuine leap second that should be followed. It has been reported that never, since the monitoring began in 2008 and whether or not a leap second should be inserted, have all NTP servers correctly set their flags on a December 31 or June 30.[49] This is one reason many NTP servers broadcast the wrong time for up to a day after a leap second insertion,[50] and it has been suggested that hackers have exploited this vulnerability.[51][52]

Four different brands of marketed navigational receivers that use data from GPS and/or GALILEO along with the Chinese BEIDOU satellites, and even some receivers that use BEIDOU satellites alone, were found to implement leap seconds one day early.[53] This was traced to the fact that BEIDOU numbers the days of the week from 0 to 6, while GPS and GALILEO number them from 1 to 7. The problem was found to exist in commercial simulators that are used by manufacturers to test their equipment.

On January 21, 2015, several models of GPS receivers implemented the leap second as soon as the announcement was broadcast by GPS, instead of waiting until the implementation date of June 30.[54]

The effect of leap seconds on the commercial sector has been described as "a nightmare".[55] Because financial markets are vulnerable to both technical and legal leap second problems, the Intercontinental Exchange, parent body to 7 clearing houses and 11 stock exchanges including the New York Stock Exchange, ceased operations for 61 minutes at the time of the June 30, 2015 leap second.[56]

Despite the publicity given to the 2015 leap second, Internet network failures occurred due to the vulnerability of at least one class of router.[57] Also, interruptions of around 40 minutes duration occurred with Twitter, Instagram, Pinterest, Netflix, Amazon, and Apple's music streaming series Beats 1.[58]

At least several versions of the Cisco NEXUS 5000 Series Operating System NX-OS (versions 5.0, 5.1, 5.2) are affected.[59]

Workarounds for leap second issues

Instead of inserting a leap second at the end of the day, Google servers implement a leap smear, extending seconds slightly over a time window prior to the leap second.[60] Amazon has announced it will follow a similar, but slightly different, pattern for the introduction of the June 30, 2015 leap second,[61] leading to another case of the proliferation of timescales, which is a concern noted in this article's section titled "Proposal to abolish leap seconds".

It has been proposed that media clients using the Real-time Transport Protocol inhibit generation or use of NTP timestamps during the leap second and the second preceding it.[62]

NIST has established a special NTP time server to deliver UT1 instead of UTC.[63] Such a server would be particularly useful in the event the ITU resolution passes and leap seconds are no longer inserted.[64] Those astronomical observatories and other users that require UT1 could run off UT1 – although in many cases these users already download UT1-UTC from the IERS, and apply corrections in software.[65]

See also

Notes

  1. ↑ The Wall Street Journal noted that the proposal was considered by a U.S. official to be a "private matter internal to the ITU", as of July 2005.[19]
  2. ↑ The FCC has posted its received comments, which can be found using their search engine for proceeding 04-286 and limiting the "received period" to those between January 27 and February 18, 2014 inclusive.[29]
  3. ↑ In addition to publishing the video of the special session,[32] the Australian Communications and Media Authority has a transcript of that session and a web page with draft content of the Conference Preparatory Meeting report and solutions for ITU-R WRC-15 Agenda Item 1.14.[33]

References

  1. 1 2 Gambis, Danie (January 5, 2015). "Bulletin C 49". Paris: IERS. Retrieved January 5, 2015.
  2. ↑ James Vincent (January 7, 2015). "2015 is getting an extra second and that's a bit of a problem for the internet". The Verge.
  3. ↑ Ptolemy; G. J. Toomer (1998). Ptolemy's Alemagest. Toomer, G. J. Princeton, New Jersey: Princeton University Press. pp. 6–7, 23, 211–216. ISBN 978-0-691-00260-6.
  4. ↑ al-Biruni (1879). The chronology of ancient nations: an English version of the Arabic text of the Athâr-ul-Bâkiya of Albîrûnî, or "Vestiges of the Past". Sachau, C. Edward. Oriental Translation Fund of Great Britain & Ireland. pp. 141–149, 158, 408, 410. Used for mean new moons, both in Hebrew calendar cycles and in equivalent astronomical cycles.
  5. ↑ Everett, J. D. (1875). Illustrations of the centimetre-gramme-second (C.G.S.) system of units. Taylor and Francis. p. 83.
  6. ↑ Pearce, J. A. (1928). "The Variability of the Rotation of the Earth". Journal of the Royal Astronomical Society of Canada 22: 145–147.
  7. ↑ Seidelmann, P. Kenneth, ed. (1992). Explanatory Supplement to the Astronomical Almanac. Mill Valley, California: University Science Books. pp. 79–80. ISBN 0-935702-68-7.
  8. 1 2 "Leap Seconds". Time Service Department, United States Naval Observatory. Retrieved December 27, 2008.
  9. ↑ Wm Markowitz (1988) 'Comparisons of ET (Solar), ET (Lunar), UT and TDT', in (eds.) A K Babcock & G A Wilkins, 'The Earth's Rotation and Reference Frames for Geodesy and Geophysics', IAU Symposia #128 (1988), at pp 413–418.
  10. ↑ DD McCarthy and AK Babcock (1986), "The Length of the Day Since 1658", Phys. Earth Planet Inter., No. 44, pp. 281-292
  11. ↑ RA Nelson, DD McCarthy, S Malys, J Levine, B Guinot, HF Fliegel, RL Beard, and TR Bartholomew, (2001) "The Leap Second: its History and Possible Future" (2001), Metrologia 38, pp 509-529
  12. 1 2 3 4 Stephenson, F.R.; Morrison, L.V. (1995). "Long-term fluctuations in the Earth's rotation: 700 BC to AD 1990". Philosophical Transactions of the Royal Society of London, Series A 351: 165–202. Bibcode:1995RSPTA.351..165S. doi:10.1098/rsta.1995.0028.
  13. ↑ McCarthy, D D; Hackman, C; Nelson, R A (2008). "The Physical Basis of the Leap Second". Astronomical Journal 136: 1906–1908. doi:10.1088/0004-6256/136/5/1906.
  14. ↑ Gambis, Daniel (July 4, 2008). "Bulletin C 36". Paris: IERS EOP PC, Observatoire de Paris. Retrieved April 18, 2010.
  15. ↑ Andrea Thompson (December 8, 2008). "2008 Will Be Just a Second Longer". Live Science. Retrieved December 29, 2008.
  16. ↑ Kevin Gross (March 2014), RTP and Leap Seconds, RFC 7164
  17. ↑ Steve Allen (June 8, 2011). "Extrapolations of the difference (TI - UT1)". ucolick.org. Retrieved February 29, 2016.
  18. ↑ Cook-Anderson, Gretchen; Beasley, Dolores (January 10, 2005). "NASA Details Earthquake Effects on the Earth". National Aeronautics and Space Administration (press release).
  19. ↑ Why the U.S. Wants To End the Link Between Time and Sun by The Wall Street Journal
  20. ↑ Leap second talks are postponed by BBC News
  21. ↑ UTC redefinition or change by Kenneth Seidelmann
  22. ↑ Cowen, Ron. (April 22, 2006). "To Leap or Not to Leap: Scientists debate a timely issue". Science News
  23. ↑ UTC might be redefined without Leap Seconds by Steve Allen
  24. ↑ "nc1985wp7a Proposed US Contribution to ITU-R WP 7A". ucolick.org.
  25. ↑ Demetrios Matsakis (August 18, 2014). "Comments on the Debate over the Proposal to Redefine UTC" (PDF).
  26. ↑ "U.S. Proposals". National Telecommunications and Information Administration.
  27. ↑ "FCC Seeks Comment On Recommendations Approved By The Advisory Committee For The 2015 World Radiocommunication Conference" (PDF). Federal Communications Commission. January 28, 2014.
  28. ↑ "Preliminary Views and Proposals Regarding WRC-15 Agenda Items" (PPT). Organization of American States.
  29. ↑ "Search for Filings Results". fcc.gov.
  30. ↑ Merali, Zeeya. (November 8, 2011). "Time is running out for the leap second". Nature News.
  31. ↑ Han, Chunhao (September 19, 2013). "Conception, Definition and Realization of Time Scale in GNSS" (PDF).
  32. ↑ Information Session on the WRC-15 agenda item 1.14 – Coordinated Universal Time (UTC). YouTube. April 15, 2015.
  33. ↑ "WRC-15 Agenda item 1.14: Coordinated Universal Time (UTC)". acma.gov.au. Archived from the original on September 8, 2015.
  34. ↑ "RESOLUTION 653 (WRC-12) Future of the Coordinated Universal Time time-scale" (PDF). International Telecommunications Union.
  35. ↑ CCTF Strategy Document (PDF), International Bureau of Weights and Measures, July 29, 2013, pp. 19–24
  36. ↑ "47th CGSIC Meeting - Timing Subcommittee" (PDF). September 25, 2007. p. 9. Retrieved November 18, 2007.
  37. ↑ "WP7D - Status of Coordinated Universal Time (UTC) study in ITU-R" (Word 2007). International Telecommunication Union – Radiocommunication Sector (ITU-R) Release: Pg.2 (Pgs.2). October 4, 2011. Retrieved October 24, 2011. To date, the BR received replies from 16 different Member States for the latest survey (out of a total of 192 Member States, 55 of which participate in the formation of UTC) - 13 being in favor of the change, 3 being contrary.
  38. ↑ "Coordinated Universal Time (UTC) to retain 'leap second'". International Telecommunications Union. 2015-11-19. Retrieved January 12, 2016.
  39. ↑ "CGSIC opinion on the redefinition of UTC now under consideration by the International Telecommunications Union (ITU)".
  40. ↑ "The proposed redefinition of Coordinated Universal Time, UTC" (PDF) (Press release). BIPM. October 13, 2011.
  41. ↑ "‘Leap Second’ Bug Wreaks Havoc Across Web". Wired. July 1, 2012.
  42. ↑ "'Leap second crashes Qantas and leaves passengers stranded'". News Limited. July 1, 2012.
  43. ↑ "Anyone else experiencing high rates of Linux server crashes during a leap second day?". Serverfault.com.
  44. ↑ "256-Week Leap Second Bug". July 2, 2013.
  45. ↑ "Motorola Oncore receivers and Leap Second bug". July 2, 2013.
  46. ↑ "Leap-second problem with older GPS receivers". November 19, 2014.
  47. ↑ "How Leap Seconds Can Interfere with GNSS Receivers". May 13, 2015.
  48. ↑ "Symmetricom TymServe 2100-GPS currently fails with GPS offset". time-nuts (Mailing list).
  49. ↑ Dr. David Malone, http://www.maths.tcd.ie/~dwmalone/time/leaps/
  50. ↑ "NTP Events". satsignal.eu.
  51. ↑ "WARNING: someone's faking a leap second tonight".
  52. ↑ Marco Marongiu (July 31, 2012). "WARNING: someone's faking a leap second tonight". Newsgroup: comp.protocols.time.ntp.
  53. ↑ "BeiDou Numbering Presents Leap-Second Issue". GPS World. March 3, 2015.
  54. ↑ "Leap Second Implementation Confuses Some Receivers". GPS World. February 2, 2015.
  55. ↑ Sellwood, Dick. "Just A Second". www.eejournal.com. Electronic Engineering Journal. Retrieved September 27, 2015.
  56. ↑ "ICE Market Update - Leap Second Impact". Intercontinental Exchange.
  57. ↑ Shulman, Eden. "Beta Boston". Boston Globe. Retrieved September 27, 2015.
  58. ↑ Sarah Knapton (July 1, 2015). "Leap Second confuses Twitter and Android". The Daily Telegraph.
  59. ↑ "Cisco Bug: CSCub38654 - N5K: Switch hang/lock up may occur due to Leap second update". Cisco. Jul 24, 2015.
  60. ↑ Christopher Pascoe (September 15, 2011). "Time, technology and leaping seconds". Google. Retrieved July 2, 2012.
  61. ↑ Jeff Barr (May 18, 2015). "Look Before You Leap – The Coming Leap Second and AWS (Updated)". Amazon Web Services.
  62. ↑ Kevin Gross (June 21, 2012). "RTP and Leap Seconds". Internet Engineering Task Force. Retrieved July 2, 2012.
  63. ↑ http://www.nist.gov/pml/div688/grp40/ut1_ntp_description.cfm
  64. ↑ Wallace, Patrick (2003). The UTC Problem and its Solution (PDF). Proceedings of Colloquium on the UTC Time Scale. Torino.
  65. ↑ Luzum, Brian (2013). "The Role of the IERS in the Leap Second" (PDF).

Further reading

External links

Wikimedia Commons has media related to Leap second.


This article is issued from Wikipedia - version of the Monday, March 07, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.