Leap second: Difference between revisions

Revision as of 08:07, 13 September 2024

Revision as of 14:54, 13 September 2024

Line 318:

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 aan 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>