How Precision Time Protocol handles leap seconds

What this post added

This post details Meta's approach to handling leap seconds within its Precision Time Protocol (PTP) infrastructure, contrasting it with traditional NTP methods. It introduces 'self-smearing' via the fbclock library, which shifts time by 1 nanosecond every 62.5 microseconds, and discusses the trade-offs of using UTC over TAI for timekeeping. The post also advocates for the industry-wide freeze of leap seconds to simplify time synchronization and improve precision.