[181466] in North American Network Operators' Group
Re: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Damian Menscher via NANOG)
Thu Jun 25 18:23:56 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <BF80D13E-D8B8-4768-A751-3DC66AF5DCA9@ono.at>
Date: Thu, 25 Jun 2015 15:23:29 -0700
To: Stefan Schlesinger <sts@ono.at>
From: Damian Menscher via NANOG <nanog@nanog.org>
Reply-To: Damian Menscher <damian@google.com>
Cc: NANOG mailing list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Wed, Jun 24, 2015 at 9:48 PM, Stefan Schlesinger <sts@ono.at> wrote:
> > On 25 Jun 2015, at 03:14, Damian Menscher via NANOG <nanog@nanog.org>
> wrote:
> >
> >
> http://googleblog.blogspot.com/2011/09/time-technology-and-leaping-seconds.html
> > comes dangerously close to your modest proposal.
>
> I wonder why Google hasn't published the patch yet. Leap smear sounds like
> the sane way to do leap seconds, and it would't break software at all,
> because time adjustments in the sub-second area are proven to work quite
> well.
>
> Btw. there seem to be a couple of public Google timeservers, I wonder
> whether could just sync time from there to get leap smearing.
>
I'd be cautious about that approach. I don't think they've been advertised
for public use, so they could go away without notice. Also, definitely
don't mix them with normal servers, as that would just confuse your clocks
(which might smear *and* leap or something equally insane).
Damian
