[177491] in North American Network Operators' Group
Re: REMINDER: Leap Second
daemon@ATHENA.MIT.EDU (Mike.)
Sun Jan 25 10:19:39 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <194715CB-3779-428C-A6C1-5444A5902E69@baylink.com>
Date: Sun, 25 Jan 2015 10:19:29 -0500
From: "Mike." <the.lists@mgm51.com>
To: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
On 1/25/2015 at 9:37 AM Jay Ashworth wrote:
|This June 30th, 235959UTC will be followed immediately by 235960UTC.
|
|What will /your/ devices do?
=============
I've always wondered why this is such a big issue, and why it's done
as it is.
In UNIX, for instance, time is measured as the number of seconds
since the UNIX epoch. imo, the counting of the number of seconds
should not be "adjusted", unless there's a time warp of some sort.
The leap second adjustment should be in the display of the time,
i.e., similar to how time zones are handled.
fwiw
