[181416] in North American Network Operators' Group
Re: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (shawn wilson)
Tue Jun 23 13:23:06 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <558933EB.6000201@foobar.org>
Date: Tue, 23 Jun 2015 13:23:04 -0400
From: shawn wilson <ag4ve.us@gmail.com>
To: Nick Hilliard <nick@foobar.org>
Cc: North American Network Operators Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Jun 23, 2015 6:26 AM, "Nick Hilliard" <nick@foobar.org> wrote:
>
>
> Blocking NTP at the NTP edge will probably work fine for most situations.
> Bear in mind that your NTP edge is not necessarily the same as your
network
> edge. E.g. you might have internal GPS / radio sources which could
> unexpectedly inject the leap second. The larger the network, the more
> likely this is to happen. Most organisations have network fossils and ntp
> is an excellent source of these. I.e. systems which work away for years
> without any problems before one day accidentally triggering meltdown
> because some developer didn't understand the subtleties of clock
monotonicity.
>
NTP causes jumps - not skews, right?
