NCCIC National Cybersecurity & Communications Integration Center NCC National Coordinating Center for Communications UNCLASSIFIED TLP: WHITE Best Practices for Leap Second Event Occurring on 31 December 2016 This paper is intended as a best practices guide to be used for the upcoming Leap Second event scheduled for Saturday, 31 December 2016. Sponsored by the Department of Homeland Security’s National Cybersecurity and Communications Integration Center in coordination with the United States Naval Observatory, National Institute of Standards and Technology, the USCG Navigation Center, and the National Coordination Office for Space-Based Positioning, Navigation and Timing. This product is intended to assist federal, state, local, and private sector organizations with preparations for Saturday, 31 December 2016 Leap Second event. The decision to add a leap second is made by the International Earth Rotation and Reference Systems Service, an international standards body, to accommodate for variations in the Earth’s rotational speed. The U.S. federal government's Global Positioning System (GPS) broadcasts leap second correction information in the navigation message. However, it is the responsibility of users to assure that their hardware and software recognizes and manages the leap second correctly; errors and equipment failures can occur when GPS receivers and clocks process the leap second signal incorrectly. Please ensure all software and firmware is up to date. Please report operational challenges you experience to the following organizations: GPS — United States Coast Guard Navigation Center (NAVCEN) 703-313-5900 or via the NAVCEN Website, http://www.navcen.uscg.gov/ under "Report a GPS Problem" NIST Time Dissemination Services — Michael Lombardi at NIST, Boulder, Colorado at 303-497-3212, or [email protected]. 1. Leap Second Introduction UNCLASSIFIED TLP: WHITE UNCLASSIFIED TLP: WHITE The Coordinated Universal Time (UTC) time standard, based on atomic clocks, is widely used for international timekeeping. UTC is the basis of legal time for most of the world, including the United States. For the DoD, UTC (USNO), UTC as realized by the U.S. Naval Observatory (USNO), is the standard for all DoD systems/operations. UTC (NIST), UTC as realized by the National Institute of Standards and Technology (NIST), is official time for civilian use. The two time scales are equivalent to within 50 nanoseconds, and for many applications either may be used. UTC must be adjusted at irregular intervals to keep it close to mean solar time, due to irregularities in Earth’s rotation. These adjustments, called leap seconds, are pre- determined. The next leap second will occur on 31 December 2016 at 23:59:59 UTC. Specifically, a positive leap second will be inserted between second 23:59:59 UTC of 31 December and second 00:00:00 UTC of 1 January 2017. This extra second is displayed on UTC clocks as 23:59:60. Historically, previous Leap Seconds have posed challenges to operations. With these challenges in mind, this best practices guide provides: • Information to prepare for the upcoming Leap Second; • Steps to resolve any operational issues; • Guidance for reporting Leap Second related operational issues. UTC is the official term for the time maintained cooperatively by many countries, using atomic clocks. The term is often used colloquially to refer to time scales based on the time zone of the prime meridian, zero longitude (e.g., military time, Zulu time, Greenwich Mean Time (GMT)). (Time scales based on astronomy [e.g., mean solar time] will differ slightly from UTC.) Local time zone offsets apply as needed. For example, the 31 December 2016 leap second will occur at 6:59:59 PM Eastern Standard Time on the East coast of the United States and 3:59:59 PM Pacific Standard Time on the West coast of the United States. NOTE: Systems that do not receive time via an external reference may require manual resetting or synchronization to maintain consistency with UTC. For more information on Leap Seconds, please see the background following the best practices. 2. Leap Second Preparation a. Check and verify leap second insertion procedures on all systems dependent on precise time to verify leap second insertion will not disrupt normal operation. UNCLASSIFIED TLP: WHITE UNCLASSIFIED TLP: WHITE b. Verify Global Positioning System (GPS) receivers are built in accordance with GPS Interface Specification IS-GPS-200H. The time disseminated by GPS is UTC (USNO). The latest specification may be found at http://www.gps.gov/technical/icwg/. These receivers should automatically adjust UTC time of day outputs to reflect leap second changes. c. Verify Network Time Protocol (NTP) servers and clients systems are built to account for leap seconds. Some vendors may offer tests than can be run prior to the leap second event. 3. Leap Second Implementation The Leap Second occurs simultaneously worldwide based on UTC day transition 31 December/1 January, irrespective of your local time zone. To implement the positive leap second, all UTC clocks will display an extra second. The date sequence of the UTC markers will be: 31 Dec 2016 23H 59M 59S 31 Dec 2016 23H 59M 60S * (extra second) Followed by: 01 Jan 2017 00H 00M 00S Note: If your clock is set to local time zones, then the above example will need to be adjusted to your local time zone. Time on NTP clients and Stratum 2 servers should be verified after the leap second insertion. Systems receiving time over NTP may have delayed responses to the leap second update depending on the software version installed. NOTE: Not all clocks implement leap seconds in the same manner as UTC above. Some may use multiple 59s or 00s verses the 60s scheme above or even just freeze the time for one second. 4. Leap Second and Global Positioning System (GPS) a. GPS receivers should be unaffected by the addition of a leap second. Those built in accordance with IS-GPS-200H should adjust for this leap second change without user intervention. However, systems that use embedded GPS receivers as time references must be designed to accommodate the occurrence of leap seconds. UNCLASSIFIED TLP: WHITE UNCLASSIFIED TLP: WHITE b. Leap seconds should not affect the use of GPS for navigation. Location is computed using GPS System Time, a time scale that is referenced to UTC as it was in 1980, without subsequent leap seconds. Only the conversion of GPS System Time to the conventional UTC time scale is affected by leap seconds. c. The GPS signal provides advanced notice to the receiver that a leap second will occur. To receive this message, ensure that a GPS receiver has been turned on at least once since 19 July 2016, and prior to 2359 on 31 December 2016, for at least 30 minutes— the cycle time of the suite of messages. This will ensure that the latest almanac is downloaded, which will contain the leap second notification information. i. Reports indicate that some receivers not built in accordance with the standard (IS-GPS-200H) have experienced problems since the notice of the scheduled future leap second was uploaded to the GPS NAV message on 19 July 2016. A one second UTC time error appeared on some receivers following this notice as the receivers effectively introduced the leap second early. The receiver manufacturer and POCs listed in this document should be notified if this problem has occurred. d. The leap second correction information is broadcast by GPS and is contained within the GPS navigation (NAV) message, sub frame 4, page 18. IS-GPS-200H sections “3.3.4 GPS Time and SV Z-Count” on page 40; “20.3.3.5.2.4 Coordinated Universal Time (UTC)” on page 123; and “30.3.3.6.2 UTC and GPS Time” on page 180 provide detailed information related to the leap second. e. The leap second correction contained within the UTC data of subframe 4, page 18 of the navigation message transmitted by satellites will change from 17s to 18s. 5. Leap Second and Network Time Protocol (NTP) Care should be taken with NTP. a. Network managers should verify their networks are utilizing a traceable NTP source. These include the NTP servers provided by NIST (see http://tf.nist.gov/tf- cgi/servers.cgi) and USNO, at: DNS IP address Location ntp.usno.navy.mil 192.5.41.40 Washington, D.C. ntp.usnogps.navy.mil 204.34.198.40 Colorado Springs, CO These NTP servers will correctly implement leap seconds. UNCLASSIFIED TLP: WHITE UNCLASSIFIED TLP: WHITE b. NTP data packets may include a leap second flag, which informs the user client software that a leap second is imminent. This allows the user client software to automatically adjust for leap seconds. c. Certain computer systems are not designed to handle the existence of leap seconds—that is, other than 86,400 seconds in a day. When leap seconds occur, they handle them in various ad hoc ways. Some IT providers plan to spread the extra second out over many hours before or after the actual leap second. Others duplicate the time stamp of 23:59:59 or 00:00:00 over two seconds. Others ignore the leap second and resynchronize to UTC at some later time. NTP servers hosted on such computer systems may disseminate inaccurate data that follow from these ad hoc approaches. These data include both the time and the leap second flag. The time may be in error for up to a day after leap second insertion. d. Users with computer systems that rely on NTP to obtain or disseminate the correct time to better than one second should take two steps. First, ensure that your NTP software is up to date. (See, e.g., http://www.ntp.org/downloads.html .) Second, ask the operators of any NTP servers that you use how their systems handle leap seconds.