Editing Leap second (section)

==Workarounds==
The most obvious workaround is to use the TAI scale for all operational purposes and convert to UTC for human-readable text. UTC can always be derived from TAI with a suitable table of leap seconds. The [[Society of Motion Picture and Television Engineers]] (SMPTE) video/audio industry standards body selected TAI for deriving timestamps of media.<ref>{{cite web|url=http://www.ieee802.org/1/files/public/docs2013/asbt-briscoe-timing-and-sync-SMPTE-0513.pdf|title=Network-Based Timing and Synchronization|author=Paul Briscoe|date=14 May 2013}}</ref> 
IEC/IEEE 60802 (Time sensitive networks) specifies TAI for all operations. Grid automation is planning to switch to TAI for global distribution of events in electrical grids.  [[Bluetooth mesh networking]] also uses TAI.<ref>{{Cite web|url=https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=429634|title=Mesh Model Bluetooth® Specification|date=13 July 2017|website=Bluetooth Technology Website|format=PDF download|access-date=14 December 2019}} See sections 5.1.1 and A.1.</ref>

Instead of inserting a leap second at the end of the day, [[Google]] servers implement a "leap smear", extending seconds slightly over a 24-hour period centered on the leap second.<ref name=google-smear>{{cite web|url=https://developers.google.com/time/smear|title=Leap Smear|publisher=Google Inc.|access-date=26 May 2023}}</ref>  Amazon followed a similar, but slightly different, pattern for the introduction of the 30 June 2015, leap second,<ref>{{cite web|url=https://aws.amazon.com/blogs/aws/look-before-you-leap-the-coming-leap-second-and-aws/|title=Look Before You Leap – The Coming Leap Second and AWS (Updated)|author1=Jeff Barr|date=18 May 2015|publisher=[[Amazon Web Services]]}}</ref> leading to another case of the proliferation of timescales. They later released an NTP service for [[Amazon Elastic Compute Cloud|EC2]] instances which performs leap smearing.<ref>{{cite web|url=https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-time-sync-service/|title=Keeping Time With Amazon Time Sync Service|author1=Randall Hunt|date=29 November 2017|publisher=[[Amazon Web Services]]|access-date=8 March 2018}}</ref> UTC-SLS was proposed as a version of UTC with linear leap smearing, but it never became standard.<ref>{{cite web |last1=Kuhn |first1=Markus |title=UTC with Smoothed Leap Seconds (UTC-SLS) |url=https://www.cl.cam.ac.uk/~mgk25/time/utc-sls/|date=2005 |website=www.cl.cam.ac.uk}}</ref>

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.<ref>{{cite ietf|rfc=7164|title=RTP and Leap Seconds|author=Kevin Gross|date=March 2014}}</ref>

NIST has established a special NTP time server to deliver UT1 instead of UTC.<ref>{{cite web |url=https://www.nist.gov/pml/time-and-frequency-division/time-services/ut1-ntp-time-dissemination |title=UT1 NTP Time Dissemination |website=[[National Institute of Standards and Technology]] |date=11 December 2015 |access-date=31 August 2019}}</ref>  Such a server would be particularly useful in the event the ITU resolution passes and leap seconds are no longer inserted.<ref>{{cite conference|first1=Patrick|last1=Wallace|year=2003|title=The UTC Problem and its Solution|book-title=Proceedings of Colloquium on the UTC Time Scale|location=Torino|url=http://www.ucolick.org/~sla/leapsecs/torino/wallace.pdf|url-status=live|archive-url=https://web.archive.org/web/20150118134330/http://www.ucolick.org/~sla/leapsecs/torino/wallace.pdf|archive-date=18 January 2015}}</ref> 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.<ref>{{cite conference|first1=Brian|last1=Luzum|title=The Role of the IERS in the Leap Second|conference=BIPM/ITU Workshop on the Future of the International Time Scale|year=2013|url=https://www.itu.int/dms_pub/itu-r/oth/0a/0e/R0A0E0000960016PDFE.pdf|url-status=live|archive-url=https://web.archive.org/web/20140715055118/https://www.itu.int/dms_pub/itu-r/oth/0a/0e/R0A0E0000960016PDFE.pdf|archive-date=15 July 2014}}</ref>