From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Jan  6 11:19:25 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB5913A6848
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Tue,  6 Jan 2009 11:19:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0NikH-U5p6Hn
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Tue,  6 Jan 2009 11:19:24 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id A615E3A68B1
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  6 Jan 2009 11:19:24 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id A169F39FA6
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  6 Jan 2009 19:19:10 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 4EDED39F8F
	for <ntpwg@lists.ntp.isc.org>; Mon,  5 Jan 2009 18:47:08 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 10289-09 for <ntpwg@lists.ntp.isc.org>;
	Mon,  5 Jan 2009 18:47:03 +0000 (UTC)
X-Greylist: delayed 3825 seconds by postgrey-1.21 at ntp1.isc.org;
	Mon, 05 Jan 2009 18:47:03 UTC
Received: from yw-out-1718.google.com (yw-out-1718.google.com [74.125.46.153])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Mon,  5 Jan 2009 18:45:47 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: by yw-out-1718.google.com with SMTP id 9so3199153ywk.36
	for <ntpwg@lists.ntp.isc.org>; Mon, 05 Jan 2009 10:45:46 -0800 (PST)
Received: by 10.100.122.8 with SMTP id u8mr11133958anc.131.1231177355742;
	Mon, 05 Jan 2009 09:42:35 -0800 (PST)
Received: by 10.100.8.3 with HTTP; Mon, 5 Jan 2009 09:42:35 -0800 (PST)
Message-ID: <3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
Date: Mon, 5 Jan 2009 11:42:35 -0600
From: "Linas Vepstas" <linasvepstas@gmail.com>
To: david@lang.hm
In-Reply-To: <alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
MIME-Version: 1.0
Content-Disposition: inline
References: <495F0672.6020708@davidnewall.com>
	<4960897D.5030603@davidnewall.com>
	<alpine.DEB.1.10.0901040310070.24563@asgard.lang.hm>
	<4961432A.80509@davidnewall.com>
	<alpine.DEB.1.10.0901041628100.25545@asgard.lang.hm>
	<49614835.7000505@davidnewall.com>
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>
	<20090105143335.GC18055@mail.local.tull.net>
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
X-Mailman-Approved-At: Tue, 06 Jan 2009 19:18:41 +0000
Cc: Robert Hancock <hancockr@shaw.ca>, Ben Goodger <goodgerster@gmail.com>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>,
	David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	Travis Crump <pretzalz@techhouse.org>, burdell@iruntheinter.net,
	Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: linasvepstas@gmail.com
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

2009/1/5  <david@lang.hm>:
> On Mon, 5 Jan 2009, Linas Vepstas wrote:
>
>>> Arguably the kernel's responsibility should be to keep track of the
>>> most fundamental representation of time possible for a machine (that's
>>> probably TAI) and it is a userspace responsibility to map from that
>>> value to other time standards including UTC,
>>
>> Yes, this really does seem like the right solution.
>>
>>> using control files
>>> which are updated as leap seconds are declared.
>>
>> Lets be clear on what "control files" means.  This does
>> *NOT* mean some config file shipped by some distro
>> for some package. That would be a horrid solution.
>> People don't install updates, patches, etc.  Distros
>> ship them late, or never, if the distro is old enough.
>>
>> A more appropriate solution would be to have
>> either the kernel or ntpd track the leap seconds
>> automatically.  First, the ntp protocol already provides
>> the needed notification of a leap second to anyone
>> who cares about it (i.e. there is no point in getting a
>> Linux distro involved in this -- a distribution mechanism
>> already exists, and works *better* than having a distro
>> do it).
>
> I disagree with this. NTP will only know about leap seconds if it was
> running and connected to a server that advertised the leap seconds during
> that month.
>
> for example, if you installed a new server today, how would it ever know
> that there was a leap second a couple of days ago?

OK, good point.  Unless your distro was less
than a few days old (unlikely), you are faced with the
same problem.  Sure, eventually, the distro will publish
an update (which will add to the existing list of 36 leap
seconds -- which is needed in any case, since no one
has a server that's been up since 1958),  but this is
unlikely to happen during this install window.

The long term solution would be write an RFC to extend
NTP to also provide TAI information -- e.g. to add a
message that indicates the current leap-second offset
between UTC and TAI.

--linas
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Jan  6 11:20:00 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 837763A6991
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Tue,  6 Jan 2009 11:20:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1b14Oga3APc5
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Tue,  6 Jan 2009 11:19:59 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id BB6883A6848
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  6 Jan 2009 11:19:59 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 0CC8639FC1
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  6 Jan 2009 19:19:47 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 60EE439F57
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 02:55:41 +0000 (UTC)
	(envelope-from johnstul.lkml@gmail.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 84035-01 for <ntpwg@lists.ntp.isc.org>;
	Tue,  6 Jan 2009 02:55:39 +0000 (UTC)
X-Greylist: delayed 1180 seconds by postgrey-1.21 at ntp1.isc.org;
	Tue, 06 Jan 2009 02:55:38 UTC
Received: from yw-out-1718.google.com (yw-out-1718.google.com [74.125.46.156])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 02:55:01 +0000 (UTC)
	(envelope-from johnstul.lkml@gmail.com)
Received: by yw-out-1718.google.com with SMTP id 9so3280990ywk.36
	for <ntpwg@lists.ntp.isc.org>; Mon, 05 Jan 2009 18:55:01 -0800 (PST)
Received: by 10.90.53.5 with SMTP id b5mr9933036aga.74.1231208838899;
	Mon, 05 Jan 2009 18:27:18 -0800 (PST)
Received: by 10.90.51.12 with HTTP; Mon, 5 Jan 2009 18:27:18 -0800 (PST)
Message-ID: <1f1b08da0901051827r57158990ic795208ba37120ad@mail.gmail.com>
Date: Mon, 5 Jan 2009 18:27:18 -0800
From: "john stultz-lkml" <johnstul.lkml@gmail.com>
To: linasvepstas@gmail.com
In-Reply-To: <3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <495F0672.6020708@davidnewall.com>
	<alpine.DEB.1.10.0901040310070.24563@asgard.lang.hm>
	<4961432A.80509@davidnewall.com>
	<alpine.DEB.1.10.0901041628100.25545@asgard.lang.hm>
	<49614835.7000505@davidnewall.com>
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>
	<20090105143335.GC18055@mail.local.tull.net>
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
X-Mailman-Approved-At: Tue, 06 Jan 2009 19:18:41 +0000
Cc: david@lang.hm, Ben Goodger <goodgerster@gmail.com>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>, zippel@linux-m68k.org,
	David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, Robert Hancock <hancockr@shaw.ca>,
	ntpwg@lists.ntp.isc.org, Travis Crump <pretzalz@techhouse.org>,
	burdell@iruntheinter.net, Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Mon, Jan 5, 2009 at 9:42 AM, Linas Vepstas <linasvepstas@gmail.com> wrote:
[snip]
> The long term solution would be write an RFC to extend
> NTP to also provide TAI information -- e.g. to add a
> message that indicates the current leap-second offset
> between UTC and TAI.

I believe Roman has already added this ability:
http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=153b5d054ac2d98ea0d86504884326b6777f683d;hp=9f14f669d18477fe3df071e2fa4da36c00acee8e

thanks
-john
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Jan  6 11:20:37 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B6C9E3A6991
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Tue,  6 Jan 2009 11:20:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 87uKAsUj3KjW
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Tue,  6 Jan 2009 11:20:37 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id EB4983A6848
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  6 Jan 2009 11:20:36 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 517F139FA3
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  6 Jan 2009 19:20:24 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 6865939F24
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 04:54:27 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 83386-08 for <ntpwg@lists.ntp.isc.org>;
	Tue,  6 Jan 2009 04:54:23 +0000 (UTC)
X-Greylist: delayed 38892 seconds by postgrey-1.21 at ntp1.isc.org;
	Tue, 06 Jan 2009 04:54:23 UTC
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 04:53:47 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: by an-out-0708.google.com with SMTP id b2so2564835ana.36
	for <ntpwg@lists.ntp.isc.org>; Mon, 05 Jan 2009 20:53:46 -0800 (PST)
Received: by 10.100.128.2 with SMTP id a2mr11452867and.93.1231217626485;
	Mon, 05 Jan 2009 20:53:46 -0800 (PST)
Received: by 10.100.8.3 with HTTP; Mon, 5 Jan 2009 20:53:46 -0800 (PST)
Message-ID: <3ae3aa420901052053m5a410671u13ecccfb7e29260c@mail.gmail.com>
Date: Mon, 5 Jan 2009 22:53:46 -0600
From: "Linas Vepstas" <linasvepstas@gmail.com>
To: "john stultz-lkml" <johnstul.lkml@gmail.com>
In-Reply-To: <1f1b08da0901051827r57158990ic795208ba37120ad@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <495F0672.6020708@davidnewall.com> <4961432A.80509@davidnewall.com>
	<alpine.DEB.1.10.0901041628100.25545@asgard.lang.hm>
	<49614835.7000505@davidnewall.com>
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>
	<20090105143335.GC18055@mail.local.tull.net>
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<1f1b08da0901051827r57158990ic795208ba37120ad@mail.gmail.com>
X-Mailman-Approved-At: Tue, 06 Jan 2009 19:18:42 +0000
Cc: david@lang.hm, Ben Goodger <goodgerster@gmail.com>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>, zippel@linux-m68k.org,
	David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, Robert Hancock <hancockr@shaw.ca>,
	ntpwg@lists.ntp.isc.org, Travis Crump <pretzalz@techhouse.org>,
	burdell@iruntheinter.net, Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: linasvepstas@gmail.com
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

2009/1/5 john stultz-lkml <johnstul.lkml@gmail.com>:
> On Mon, Jan 5, 2009 at 9:42 AM, Linas Vepstas <linasvepstas@gmail.com> wrote:
> [snip]
>> The long term solution would be write an RFC to extend
>> NTP to also provide TAI information -- e.g. to add a
>> message that indicates the current leap-second offset
>> between UTC and TAI.
>
> I believe Roman has already added this ability:
> http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=153b5d054ac2d98ea0d86504884326b6777f683d;hp=9f14f669d18477fe3df071e2fa4da36c00acee8e

Well, you're answering a different statment than what
I was talking about -- I wanted to make sure that TAI
information was available via NTP -- this has nothing
to do with the kernel, and would be something available
to all operating systems.

Anyway -- I'm looking at the patch you reference, and
maybe I'm being dumb -- but -- I think I see a bug.

case TIME_DEL decrements TAI, but TIME_INS does
not increment it. Instead, there's a lonely increment in
TIME_OOP which seems wrong.  ??


--linas
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Jan  6 11:21:06 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 725013A6882
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Tue,  6 Jan 2009 11:21:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id G8dsHZM0ihNV
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Tue,  6 Jan 2009 11:21:05 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 5EFF73A67F3
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  6 Jan 2009 11:21:05 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 9EB9739FA7
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  6 Jan 2009 19:20:52 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 5CEA039F83
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 05:01:15 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 84035-09 for <ntpwg@lists.ntp.isc.org>;
	Tue,  6 Jan 2009 05:01:07 +0000 (UTC)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.251])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 05:00:30 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: by an-out-0708.google.com with SMTP id b2so2565411ana.36
	for <ntpwg@lists.ntp.isc.org>; Mon, 05 Jan 2009 21:00:30 -0800 (PST)
Received: by 10.100.134.16 with SMTP id h16mr11451741and.42.1231218030222;
	Mon, 05 Jan 2009 21:00:30 -0800 (PST)
Received: by 10.100.8.3 with HTTP; Mon, 5 Jan 2009 21:00:30 -0800 (PST)
Message-ID: <3ae3aa420901052100q18afb1d0x19b85355a07d5dce@mail.gmail.com>
Date: Mon, 5 Jan 2009 23:00:30 -0600
From: "Linas Vepstas" <linasvepstas@gmail.com>
To: "john stultz-lkml" <johnstul.lkml@gmail.com>
In-Reply-To: <3ae3aa420901052053m5a410671u13ecccfb7e29260c@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <495F0672.6020708@davidnewall.com>
	<alpine.DEB.1.10.0901041628100.25545@asgard.lang.hm>
	<49614835.7000505@davidnewall.com>
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>
	<20090105143335.GC18055@mail.local.tull.net>
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<1f1b08da0901051827r57158990ic795208ba37120ad@mail.gmail.com>
	<3ae3aa420901052053m5a410671u13ecccfb7e29260c@mail.gmail.com>
X-Mailman-Approved-At: Tue, 06 Jan 2009 19:18:42 +0000
Cc: david@lang.hm, Ben Goodger <goodgerster@gmail.com>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>, zippel@linux-m68k.org,
	David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, Robert Hancock <hancockr@shaw.ca>,
	ntpwg@lists.ntp.isc.org, Travis Crump <pretzalz@techhouse.org>,
	burdell@iruntheinter.net, Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: linasvepstas@gmail.com
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Oops.

2009/1/5 Linas Vepstas <linasvepstas@gmail.com>:
> 2009/1/5 john stultz-lkml <johnstul.lkml@gmail.com>:
>> On Mon, Jan 5, 2009 at 9:42 AM, Linas Vepstas <linasvepstas@gmail.com> wrote:
>> [snip]
>>> The long term solution would be write an RFC to extend
>>> NTP to also provide TAI information -- e.g. to add a
>>> message that indicates the current leap-second offset
>>> between UTC and TAI.
>>
>> I believe Roman has already added this ability:
>> http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=153b5d054ac2d98ea0d86504884326b6777f683d;hp=9f14f669d18477fe3df071e2fa4da36c00acee8e
>
> Well, you're answering a different statment than what
> I was talking about -- I wanted to make sure that TAI
> information was available via NTP -- this has nothing
> to do with the kernel, and would be something available
> to all operating systems.
>
> Anyway -- I'm looking at the patch you reference, and
> maybe I'm being dumb -- but -- I think I see a bug.
>
> case TIME_DEL decrements TAI, but TIME_INS does
> not increment it. Instead, there's a lonely increment in
> TIME_OOP which seems wrong.  ??

Never mind. Sorry, I'm wrong, the code looks right.
Time to stop reading email, and go to bed. :-)

--linas
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Jan  7 09:06:57 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CC543A6A7B
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed,  7 Jan 2009 09:06:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 84c8rqKBlQvu
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Wed,  7 Jan 2009 09:06:56 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 953363A680A
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 09:06:56 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 4627339F98
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 17:06:42 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 8F5E739F37
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 10:11:04 +0000 (UTC)
	(envelope-from davidn@davidnewall.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 92863-07 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 10:10:37 +0000 (UTC)
X-Greylist: delayed 338 seconds by postgrey-1.21 at ntp1.isc.org;
	Wed, 07 Jan 2009 10:10:37 UTC
Received: from hawking.rebel.net.au (hawking.rebel.net.au [203.20.69.83])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 10:10:02 +0000 (UTC)
	(envelope-from davidn@davidnewall.com)
Received: from [192.168.0.5] (ppp121-45-110-114.lns10.adl6.internode.on.net
	[::ffff:121.45.110.114])
	(AUTH: PLAIN davidn, SSL: TLSv1/SSLv3,256bits,AES256-SHA)
	by hawking.rebel.net.au with esmtp; Wed, 07 Jan 2009 20:34:09 +1030
	id 006E0262.49647E19.00003713
Message-ID: <49647E0F.9030008@davidnewall.com>
Date: Wed, 07 Jan 2009 20:33:59 +1030
From: David Newall <davidn@davidnewall.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: linasvepstas@gmail.com
References: <495F0672.6020708@davidnewall.com>
	<4961432A.80509@davidnewall.com>	
	<alpine.DEB.1.10.0901041628100.25545@asgard.lang.hm>	
	<49614835.7000505@davidnewall.com>	
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>	
	<20090105143335.GC18055@mail.local.tull.net>	
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>	
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>	
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>	
	<49642674.9080703@ntp.isc.org>
	<3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
In-Reply-To: <3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
X-Mailman-Approved-At: Wed, 07 Jan 2009 17:06:04 +0000
Cc: david@lang.hm, Robert Hancock <hancockr@shaw.ca>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>,
	Ben Goodger <goodgerster@gmail.com>, mayer@ntp.isc.org,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	Travis Crump <pretzalz@techhouse.org>, burdell@iruntheinter.net,
	Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Linas Vepstas wrote:
> Currently, the Linux kernel keeps time in UTC. This means
> that it must take special actions to tick twice when a leap
> second comes by.

Except it doesn't have to tick twice.  Refer to
http://lkml.org/lkml/2009/1/7/78 in which I show that a time_t (what
time() returns) counts leap seconds (According to Bernstein this is what
UTC means), and using zoneinfo, the library processes leap seconds
correctly.

I just realised that the Notes in man 2 time are confusing and probably
unnecessary.  Suffice to say that (assuming correctly configured
zoneinfo) time() returns the number of seconds elapsed since start 1970.
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Jan  7 09:09:13 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E2E63A6843
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed,  7 Jan 2009 09:09:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5kQABIstF6g1
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Wed,  7 Jan 2009 09:09:12 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 359933A6828
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 09:09:12 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 4EE2039F62
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 17:08:59 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 44C7039F37
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 19:55:10 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 91106-07 for <ntpwg@lists.ntp.isc.org>;
	Tue,  6 Jan 2009 19:54:49 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 19:54:49 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail2.ntp.org (Postfix) with ESMTP id 2B6D7398AE
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 19:54:10 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n06JegIp038606;
	Tue, 6 Jan 2009 12:40:42 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Tue, 06 Jan 2009 12:40:55 -0700 (MST)
Message-Id: <20090106.124055.143671472.imp@bsdimp.com>
To: linasvepstas@gmail.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <3ae3aa420901052053m5a410671u13ecccfb7e29260c@mail.gmail.com>
References: <3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<1f1b08da0901051827r57158990ic795208ba37120ad@mail.gmail.com>
	<3ae3aa420901052053m5a410671u13ecccfb7e29260c@mail.gmail.com>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Mailman-Approved-At: Wed, 07 Jan 2009 17:08:15 +0000
Cc: david@lang.hm, goodgerster@gmail.com, kyle@moffetthome.net,
	slashdot@jameshallam.info, zippel@linux-m68k.org,
	davidn@davidnewall.com, linux-kernel@vger.kernel.org,
	hancockr@shaw.ca, ntpwg@lists.ntp.isc.org,
	pretzalz@techhouse.org, burdell@iruntheinter.net,
	johnstul.lkml@gmail.com, nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message: <3ae3aa420901052053m5a410671u13ecccfb7e29260c@mail.gmail.com>
            "Linas Vepstas" <linasvepstas@gmail.com> writes:
: 2009/1/5 john stultz-lkml <johnstul.lkml@gmail.com>:
: > On Mon, Jan 5, 2009 at 9:42 AM, Linas Vepstas <linasvepstas@gmail.com> wrote:
: > [snip]
: >> The long term solution would be write an RFC to extend
: >> NTP to also provide TAI information -- e.g. to add a
: >> message that indicates the current leap-second offset
: >> between UTC and TAI.
: >
: > I believe Roman has already added this ability:
: > http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=153b5d054ac2d98ea0d86504884326b6777f683d;hp=9f14f669d18477fe3df071e2fa4da36c00acee8e
: 
: Well, you're answering a different statment than what
: I was talking about -- I wanted to make sure that TAI
: information was available via NTP -- this has nothing
: to do with the kernel, and would be something available
: to all operating systems.
: 
: Anyway -- I'm looking at the patch you reference, and
: maybe I'm being dumb -- but -- I think I see a bug.
: 
: case TIME_DEL decrements TAI, but TIME_INS does
: not increment it. Instead, there's a lonely increment in
: TIME_OOP which seems wrong.  ??

No.  That's right.  The increment doesn't happen until the leap second
has happened.  The TIME_OOP exists to increment the TAI offset at the
right time.  The decrement would happen right away, since the second
is deleted at the end of :58.

I had to draw lots of pictures when I was working this code out in
FreeBSD.

Warner
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Jan  7 09:10:26 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 223043A6828
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed,  7 Jan 2009 09:10:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HfhPIblmgbxO
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Wed,  7 Jan 2009 09:10:24 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id EBDD23A680A
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 09:10:24 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 0F11D39F67
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 17:10:12 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 94E0739F24
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 19:58:31 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 94699-06 for <ntpwg@lists.ntp.isc.org>;
	Tue,  6 Jan 2009 19:58:13 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 19:58:13 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail2.ntp.org (Postfix) with ESMTP id DC790398AE
	for <ntpwg@lists.ntp.isc.org>; Tue,  6 Jan 2009 19:57:36 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n06JoLOu038982;
	Tue, 6 Jan 2009 12:50:21 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Tue, 06 Jan 2009 12:50:34 -0700 (MST)
Message-Id: <20090106.125034.63059204.imp@bsdimp.com>
To: linasvepstas@gmail.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
References: <3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Mailman-Approved-At: Wed, 07 Jan 2009 17:08:16 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	davidn@davidnewall.com, linux-kernel@vger.kernel.org,
	ntpwg@lists.ntp.isc.org, pretzalz@techhouse.org,
	burdell@iruntheinter.net, nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message: <3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
            "Linas Vepstas" <linasvepstas@gmail.com> writes:
: 2009/1/5  <david@lang.hm>:
: > On Mon, 5 Jan 2009, Linas Vepstas wrote:
: >
: >>> Arguably the kernel's responsibility should be to keep track of the
: >>> most fundamental representation of time possible for a machine (that's
: >>> probably TAI) and it is a userspace responsibility to map from that
: >>> value to other time standards including UTC,
: >>
: >> Yes, this really does seem like the right solution.
: >>
: >>> using control files
: >>> which are updated as leap seconds are declared.
: >>
: >> Lets be clear on what "control files" means.  This does
: >> *NOT* mean some config file shipped by some distro
: >> for some package. That would be a horrid solution.
: >> People don't install updates, patches, etc.  Distros
: >> ship them late, or never, if the distro is old enough.
: >>
: >> A more appropriate solution would be to have
: >> either the kernel or ntpd track the leap seconds
: >> automatically.  First, the ntp protocol already provides
: >> the needed notification of a leap second to anyone
: >> who cares about it (i.e. there is no point in getting a
: >> Linux distro involved in this -- a distribution mechanism
: >> already exists, and works *better* than having a distro
: >> do it).
: >
: > I disagree with this. NTP will only know about leap seconds if it was
: > running and connected to a server that advertised the leap seconds during
: > that month.
: >
: > for example, if you installed a new server today, how would it ever know
: > that there was a leap second a couple of days ago?
: 
: OK, good point.  Unless your distro was less
: than a few days old (unlikely), you are faced with the
: same problem.  Sure, eventually, the distro will publish
: an update (which will add to the existing list of 36 leap

List of 24 leap seconds.  Although the delta is 34 right now, the
first 10 leap seconds were done as tiny steps (~50-100ms) plus
frequency offsets.  Well, the first 'leap' was 1.4228180s on Jan 1,
1961.  Everybody assumes that those seconds don't exist to simplify
things (or that there was simply a 10s step between TAI and UTC on
1-Jan-1972).  The leapsecond file from NIST doesn't even have them.

: seconds -- which is needed in any case, since no one
: has a server that's been up since 1958),  but this is
: unlikely to happen during this install window.
: 
: The long term solution would be write an RFC to extend
: NTP to also provide TAI information -- e.g. to add a
: message that indicates the current leap-second offset
: between UTC and TAI.

I'd love that.  There's likely going to be some resistance to that
because the leapfile is available via the crypto-authenticated means.
However, there's no real-time information available...  Also, there
are many reference clocks that would need this information plugged
into it somehow (IRIG doesn't report leap seconds in any meaningful[*]
way, let alone UTC-TAI offset).

[*] Some IRIG extensions do support reporting leap seconds at the end
of the hour, but that's too late...

Warner
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Jan  7 09:10:58 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 129533A6828
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed,  7 Jan 2009 09:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level: 
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gcfkWTaod+SR
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Wed,  7 Jan 2009 09:10:57 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 3EF453A680A
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 09:10:57 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 60F6839F5A
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 17:10:44 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 9A63139F5D
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 16:05:17 +0000 (UTC)
	(envelope-from johnstul.lkml@gmail.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 40666-03 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 16:04:53 +0000 (UTC)
X-Greylist: delayed 135414 seconds by postgrey-1.21 at ntp1.isc.org;
	Wed, 07 Jan 2009 16:04:52 UTC
Received: from yx-out-1718.google.com (yx-out-1718.google.com [74.125.44.154])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 16:04:15 +0000 (UTC)
	(envelope-from johnstul.lkml@gmail.com)
Received: by yx-out-1718.google.com with SMTP id 4so3594027yxp.36
	for <ntpwg@lists.ntp.isc.org>; Wed, 07 Jan 2009 08:04:14 -0800 (PST)
Received: by 10.90.35.9 with SMTP id i9mr10251217agi.100.1231344254575;
	Wed, 07 Jan 2009 08:04:14 -0800 (PST)
Received: by 10.90.51.12 with HTTP; Wed, 7 Jan 2009 08:04:14 -0800 (PST)
Message-ID: <1f1b08da0901070804t163e111fj6664adbfc5f3a76e@mail.gmail.com>
Date: Wed, 7 Jan 2009 08:04:14 -0800
From: "john stultz" <johnstul@us.ibm.com>
To: mayer@ntp.isc.org
In-Reply-To: <4964BD76.9090700@ntp.isc.org>
MIME-Version: 1.0
Content-Disposition: inline
References: <495F0672.6020708@davidnewall.com>
	<49614835.7000505@davidnewall.com>
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>
	<20090105143335.GC18055@mail.local.tull.net>
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<49642674.9080703@ntp.isc.org>
	<3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
	<4964BD76.9090700@ntp.isc.org>
X-Google-Sender-Auth: 9b307ddecec90c80
X-Mailman-Approved-At: Wed, 07 Jan 2009 17:08:55 +0000
Cc: david@lang.hm, Robert Hancock <hancockr@shaw.ca>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>,
	Ben Goodger <goodgerster@gmail.com>, David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	Travis Crump <pretzalz@techhouse.org>, burdell@iruntheinter.net,
	linasvepstas@gmail.com, Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Wed, Jan 7, 2009 at 6:34 AM, Danny Mayer <mayer@ntp.isc.org> wrote:
> I'd much rather you spend the time tackling the clock interrupt losses
> that many of our Linux users complain about. See:
> https://support.ntp.org/bin/view/Support/KnownOsIssues#Section_9.2.4.
> for some of the gorier details. I'm sure you don't really want us
> recommending that they set HZ=100 in the kernel to alleviate the problem.

I believe the lost tick issue as well as the HZ=100 suggestions at the
page above are out of date for 2.6.21 and higher kernels as the
generic timekeeping rework addressed these problems.

Please let me know if you're still seeing any such issues with NTP.

thanks
-john
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Jan  7 09:12:29 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 351383A6A7B
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed,  7 Jan 2009 09:12:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qKCFdQOeKYtY
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Wed,  7 Jan 2009 09:12:28 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 394CE3A6802
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 09:12:28 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 622A939F77
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 17:12:15 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 40EED39F5A
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 03:51:05 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 49666-04 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 03:50:57 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 03:50:56 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from mail.antoniuk.md (mail.antoniuk.md [65.86.158.146])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail2.ntp.org (Postfix) with ESMTP id 495D3398AE;
	Wed,  7 Jan 2009 03:50:56 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from cust-63-209-235-138.bos-dynamic.gis.net ([63.209.235.138]
	helo=[10.10.10.101])
	by mail.antoniuk.md with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <mayer@ntp.isc.org>)
	id 1LKPQu-0004CM-B6; Tue, 06 Jan 2009 22:50:16 -0500
Message-ID: <49642674.9080703@ntp.isc.org>
Date: Tue, 06 Jan 2009 22:50:12 -0500
From: Danny Mayer <mayer@ntp.isc.org>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: linasvepstas@gmail.com
References: <495F0672.6020708@davidnewall.com>	<4960897D.5030603@davidnewall.com>	<alpine.DEB.1.10.0901040310070.24563@asgard.lang.hm>	<4961432A.80509@davidnewall.com>	<alpine.DEB.1.10.0901041628100.25545@asgard.lang.hm>	<49614835.7000505@davidnewall.com>	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>	<20090105143335.GC18055@mail.local.tull.net>	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
In-Reply-To: <3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
X-kostecke.net-MailScanner: Found to be clean
X-kostecke.net-MailScanner-From: mayer@ntp.isc.org
X-Mailman-Approved-At: Wed, 07 Jan 2009 17:11:40 +0000
Cc: david@lang.hm, Robert Hancock <hancockr@shaw.ca>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>,
	Ben Goodger <goodgerster@gmail.com>, David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	Travis Crump <pretzalz@techhouse.org>, burdell@iruntheinter.net,
	Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mayer@ntp.isc.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Linas Vepstas wrote:
> 2009/1/5  <david@lang.hm>:
>> On Mon, 5 Jan 2009, Linas Vepstas wrote:
>>
>>>> Arguably the kernel's responsibility should be to keep track of the
>>>> most fundamental representation of time possible for a machine (that's
>>>> probably TAI) and it is a userspace responsibility to map from that
>>>> value to other time standards including UTC,
>>> Yes, this really does seem like the right solution.
>>>
>>>> using control files
>>>> which are updated as leap seconds are declared.
>>> Lets be clear on what "control files" means.  This does
>>> *NOT* mean some config file shipped by some distro
>>> for some package. That would be a horrid solution.
>>> People don't install updates, patches, etc.  Distros
>>> ship them late, or never, if the distro is old enough.
>>>
>>> A more appropriate solution would be to have
>>> either the kernel or ntpd track the leap seconds
>>> automatically.  First, the ntp protocol already provides
>>> the needed notification of a leap second to anyone
>>> who cares about it (i.e. there is no point in getting a
>>> Linux distro involved in this -- a distribution mechanism
>>> already exists, and works *better* than having a distro
>>> do it).
>> I disagree with this. NTP will only know about leap seconds if it was
>> running and connected to a server that advertised the leap seconds during
>> that month.
>>
>> for example, if you installed a new server today, how would it ever know
>> that there was a leap second a couple of days ago?

Because it gets it's time from an upstream server that already has
incorporated the leap second so it doesn't really need to know that the
leap second happened a few days ago or even a few years ago.

> OK, good point.  Unless your distro was less
> than a few days old (unlikely), you are faced with the
> same problem.  Sure, eventually, the distro will publish
> an update (which will add to the existing list of 36 leap
> seconds -- which is needed in any case, since no one
> has a server that's been up since 1958),  but this is
> unlikely to happen during this install window.
> 

This is nonsense. That's not how NTP works.

> The long term solution would be write an RFC to extend
> NTP to also provide TAI information -- e.g. to add a
> message that indicates the current leap-second offset
> between UTC and TAI.
> 
> --linas

I don't know what this discussion is really about and why this was sent
  to the working group in the middle of the discussion, but there is no
need for NTP to provide TAI information since NTP only uses UTC. Leap
Seconds are automatically signaled  and incorporated when they become
due. If you don't have NTP running for some reason when a leap second is
signaled it doesn't matter since your server source will already have
incorporated the leap second so the NTP packet includes the timestamps
that include the leap second adjustment.

Operating Systems use UTC and not TAI by universal agreement and the
ones that don't are extremely rare.

Why don't you tell us what the real problem is instead of telling us
that you need TAI offset information?

Danny
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Jan  7 09:13:02 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3FAAD3A6A84
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed,  7 Jan 2009 09:13:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 41CepxiKA-ts
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Wed,  7 Jan 2009 09:13:01 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 5D7423A6A7B
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 09:13:01 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 8121739FA0
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 17:12:48 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 1B57C39F7F
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 04:53:08 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 49666-08 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 04:52:57 +0000 (UTC)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 04:52:21 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: by an-out-0708.google.com with SMTP id b2so2746557ana.36
	for <ntpwg@lists.ntp.isc.org>; Tue, 06 Jan 2009 20:52:20 -0800 (PST)
Received: by 10.100.163.15 with SMTP id l15mr12185958ane.128.1231303940588;
	Tue, 06 Jan 2009 20:52:20 -0800 (PST)
Received: by 10.100.8.3 with HTTP; Tue, 6 Jan 2009 20:52:20 -0800 (PST)
Message-ID: <3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
Date: Tue, 6 Jan 2009 22:52:20 -0600
From: "Linas Vepstas" <linasvepstas@gmail.com>
To: mayer@ntp.isc.org
In-Reply-To: <49642674.9080703@ntp.isc.org>
MIME-Version: 1.0
Content-Disposition: inline
References: <495F0672.6020708@davidnewall.com> <4961432A.80509@davidnewall.com>
	<alpine.DEB.1.10.0901041628100.25545@asgard.lang.hm>
	<49614835.7000505@davidnewall.com>
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>
	<20090105143335.GC18055@mail.local.tull.net>
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<49642674.9080703@ntp.isc.org>
X-Mailman-Approved-At: Wed, 07 Jan 2009 17:11:23 +0000
Cc: david@lang.hm, Robert Hancock <hancockr@shaw.ca>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>,
	Ben Goodger <goodgerster@gmail.com>, David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	Travis Crump <pretzalz@techhouse.org>, burdell@iruntheinter.net,
	Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: linasvepstas@gmail.com
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

2009/1/6 Danny Mayer <mayer@ntp.isc.org>:
Hi,

> I don't know what this discussion is really about and why this was sent
>  to the working group in the middle of the discussion, but there is no
> need for NTP to provide TAI information since NTP only uses UTC. Leap
> Seconds are automatically signaled  and incorporated when they become
> due. If you don't have NTP running for some reason when a leap second is
> signaled it doesn't matter since your server source will already have
> incorporated the leap second so the NTP packet includes the timestamps
> that include the leap second adjustment.
>
> Operating Systems use UTC and not TAI by universal agreement and the
> ones that don't are extremely rare.
>
> Why don't you tell us what the real problem is instead of telling us
> that you need TAI offset information?

Currently, the Linux kernel keeps time in UTC. This means
that it must take special actions to tick twice when a leap
second comes by.  Due to a (stupid) bug, some fraction
of linux systems crashed; this includes everything from
laptops to servers, to DVR's,  to cell phones and cell
phone towers. There's now a fix for this.

However, during the discussion, the idea came out that
maybe keeping UTC time in the kernel is just plain stupid.
So there's this idea floating around that maybe the kernel
should keep TAI time instead. The hope is that this will
reduce the complexity in the kernel, and push it out to
user space, "where it belongs" (to repeat a well-worn
mantra).

However, *if* we were to kick UTC out of the kernel,
and push it to user-land, then, of course, there's a
different problem: how does the kernel know what the
correct TAI time is?  As your reply makes abundantly
clear, NTP is not a good source for TAI information.

The comments which you labelled as "non-sense" were
a mis-understanding of  a discussion of a particular issue
that would arise if the kernel were to keep TAI -- if it did,
then user-space systems would need to have a reliable
source for leap-seconds. Since NTP does not
provide this, there was discussion about how that
could be worked-around. This then lead to the comment
that, "gee, wouldn't the right long-term solution be that
NTP provide TAI info?"

Clearly, it would be a lot of work to get the kernel to keep
TAI instead of UTC, so this is not, at this time, a "serious
proposal".  But if it were possible, and all the various
little issues that result were solvable, then it does seem
like a better long-term solution.

--linas

p.s. the opinions above are not my own; I'm just
summarizing the points made by the most vocal
posters to this list.
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Jan  7 09:13:38 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A7F73A6A13
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed,  7 Jan 2009 09:13:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Sgfisso1zrqV
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Wed,  7 Jan 2009 09:13:37 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 3B1A33A6802
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 09:13:37 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 51AD839FAF
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 17:13:24 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id C8B2139F63
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 14:35:52 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 29745-04 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 14:35:39 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 14:35:38 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from mail.antoniuk.md (mail.antoniuk.md [65.86.158.146])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail2.ntp.org (Postfix) with ESMTP id F2E08398CD;
	Wed,  7 Jan 2009 14:35:37 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from [198.22.153.32] (helo=[10.60.98.32])
	by mail.antoniuk.md with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <mayer@ntp.isc.org>)
	id 1LKZUt-0001CZ-8x; Wed, 07 Jan 2009 09:35:03 -0500
Message-ID: <4964BD76.9090700@ntp.isc.org>
Date: Wed, 07 Jan 2009 09:34:30 -0500
From: Danny Mayer <mayer@ntp.isc.org>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: linasvepstas@gmail.com
References: <495F0672.6020708@davidnewall.com>
	<4961432A.80509@davidnewall.com>	
	<alpine.DEB.1.10.0901041628100.25545@asgard.lang.hm>	
	<49614835.7000505@davidnewall.com>	
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>	
	<20090105143335.GC18055@mail.local.tull.net>	
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>	
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>	
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>	
	<49642674.9080703@ntp.isc.org>
	<3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
In-Reply-To: <3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
X-kostecke.net-MailScanner: Found to be clean
X-kostecke.net-MailScanner-From: mayer@ntp.isc.org
X-Mailman-Approved-At: Wed, 07 Jan 2009 17:11:40 +0000
Cc: david@lang.hm, Robert Hancock <hancockr@shaw.ca>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>,
	Ben Goodger <goodgerster@gmail.com>, David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	Travis Crump <pretzalz@techhouse.org>, burdell@iruntheinter.net,
	Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mayer@ntp.isc.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Linas Vepstas wrote:
> 2009/1/6 Danny Mayer <mayer@ntp.isc.org>:
> Hi,
> 
>> I don't know what this discussion is really about and why this was sent
>>  to the working group in the middle of the discussion, but there is no
>> need for NTP to provide TAI information since NTP only uses UTC. Leap
>> Seconds are automatically signaled  and incorporated when they become
>> due. If you don't have NTP running for some reason when a leap second is
>> signaled it doesn't matter since your server source will already have
>> incorporated the leap second so the NTP packet includes the timestamps
>> that include the leap second adjustment.
>>
>> Operating Systems use UTC and not TAI by universal agreement and the
>> ones that don't are extremely rare.
>>
>> Why don't you tell us what the real problem is instead of telling us
>> that you need TAI offset information?
> 
> Currently, the Linux kernel keeps time in UTC. This means
> that it must take special actions to tick twice when a leap
> second comes by.  Due to a (stupid) bug, some fraction
> of linux systems crashed; this includes everything from
> laptops to servers, to DVR's,  to cell phones and cell
> phone towers. There's now a fix for this.
> 
> However, during the discussion, the idea came out that
> maybe keeping UTC time in the kernel is just plain stupid.
> So there's this idea floating around that maybe the kernel
> should keep TAI time instead. The hope is that this will
> reduce the complexity in the kernel, and push it out to
> user space, "where it belongs" (to repeat a well-worn
> mantra).
> 
> However, *if* we were to kick UTC out of the kernel,
> and push it to user-land, then, of course, there's a
> different problem: how does the kernel know what the
> correct TAI time is?  As your reply makes abundantly
> clear, NTP is not a good source for TAI information.
> 
> The comments which you labelled as "non-sense" were
> a mis-understanding of  a discussion of a particular issue
> that would arise if the kernel were to keep TAI -- if it did,
> then user-space systems would need to have a reliable
> source for leap-seconds. Since NTP does not
> provide this, there was discussion about how that
> could be worked-around. This then lead to the comment
> that, "gee, wouldn't the right long-term solution be that
> NTP provide TAI info?"

It was nonsense because the summary didn't contain all of the
information required to provide context and you copied the Working Group
in the middle of all this.

NTP can provide leap-second information via an autokey protocol request,
 see Section 10.6 Leapseconds Values Message (LEAP)
http://www.ietf.org/internet-drafts/draft-ietf-ntp-autokey-04.txt but
that means you need to have autokey set up with another NTP server and
that means adding infrastructure that you probably don't want and are
not prepared to handle.

> 
> Clearly, it would be a lot of work to get the kernel to keep
> TAI instead of UTC, so this is not, at this time, a "serious
> proposal".  But if it were possible, and all the various
> little issues that result were solvable, then it does seem
> like a better long-term solution.
> 

This is a *lot* more complicated than you might think. If you are
thinking of implementing this similarly to the way timezone information
is added for display purposes, you need the whole list of leap seconds
and when the change happened since you now have to look at a timestamp
and see when it was and then apply all of the leapseconds up to that
point in time and none of the leapseconds beyond that. In addition, you
have legacy files that have UTC timestamps on them so you would need to
distinguish between UTC (legacy) and TAI timestamps in the file system
among other places (anywhere where a timestamp exists) and what would
you do about database tables which contain timestamps? The list goes on.

I'd much rather you spend the time tackling the clock interrupt losses
that many of our Linux users complain about. See:
https://support.ntp.org/bin/view/Support/KnownOsIssues#Section_9.2.4.
for some of the gorier details. I'm sure you don't really want us
recommending that they set HZ=100 in the kernel to alleviate the problem.

Danny

> --linas
> 
> p.s. the opinions above are not my own; I'm just
> summarizing the points made by the most vocal
> posters to this list.
> 
> 

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Jan  7 09:14:36 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 49F9A3A6A6E
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed,  7 Jan 2009 09:14:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aH+FosW--b1X
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Wed,  7 Jan 2009 09:14:35 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 43EE23A6802
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 09:14:35 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 55DD239F7E
	for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  7 Jan 2009 17:14:22 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 1907F39F37
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 15:43:34 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 29745-09 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 15:43:30 +0000 (UTC)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 15:42:53 +0000 (UTC)
	(envelope-from linasvepstas@gmail.com)
Received: by an-out-0708.google.com with SMTP id b2so2808936ana.36
	for <ntpwg@lists.ntp.isc.org>; Wed, 07 Jan 2009 07:42:53 -0800 (PST)
Received: by 10.100.128.20 with SMTP id a20mr12501913and.148.1231342973261;
	Wed, 07 Jan 2009 07:42:53 -0800 (PST)
Received: by 10.100.8.3 with HTTP; Wed, 7 Jan 2009 07:42:53 -0800 (PST)
Message-ID: <3ae3aa420901070742t8639479qe52cdb615bf46237@mail.gmail.com>
Date: Wed, 7 Jan 2009 09:42:53 -0600
From: "Linas Vepstas" <linasvepstas@gmail.com>
To: mayer@ntp.isc.org
In-Reply-To: <4964BD76.9090700@ntp.isc.org>
MIME-Version: 1.0
Content-Disposition: inline
References: <495F0672.6020708@davidnewall.com>
	<49614835.7000505@davidnewall.com>
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>
	<20090105143335.GC18055@mail.local.tull.net>
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<49642674.9080703@ntp.isc.org>
	<3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
	<4964BD76.9090700@ntp.isc.org>
X-Mailman-Approved-At: Wed, 07 Jan 2009 17:11:23 +0000
Cc: david@lang.hm, Robert Hancock <hancockr@shaw.ca>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>,
	Ben Goodger <goodgerster@gmail.com>, David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	Travis Crump <pretzalz@techhouse.org>, burdell@iruntheinter.net,
	Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: linasvepstas@gmail.com
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Thanks for the reply.

2009/1/7 Danny Mayer <mayer@ntp.isc.org>:
> Linas Vepstas wrote:
>> 2009/1/6 Danny Mayer <mayer@ntp.isc.org>:
>>> Why don't you tell us what the real problem is instead of telling us
>>> that you need TAI offset information?
>>
>> Currently, the Linux kernel keeps time in UTC. This means
>> that it must take special actions to tick twice when a leap
>> second comes by.  Due to a (stupid) bug, some fraction
>> of linux systems crashed; this includes everything from
>> laptops to servers, to DVR's,  to cell phones and cell
>> phone towers. There's now a fix for this.
>>
>> However, during the discussion, the idea came out that
>> maybe keeping UTC time in the kernel is just plain stupid.
>> So there's this idea floating around that maybe the kernel
>> should keep TAI time instead. The hope is that this will
>> reduce the complexity in the kernel, and push it out to
>> user space, "where it belongs" (to repeat a well-worn
>> mantra).
>>
>> However, *if* we were to kick UTC out of the kernel,
>> and push it to user-land, then, of course, there's a
>> different problem: how does the kernel know what the
>> correct TAI time is?  As your reply makes abundantly
>> clear, NTP is not a good source for TAI information.

[...]

>>   a discussion of a particular issue
>> that would arise if the kernel were to keep TAI -- if it did,
>> then user-space systems would need to have a reliable
>> source for leap-seconds. Since NTP does not
>> provide this, there was discussion about how that
>> could be worked-around. This then lead to the comment
>> that, "gee, wouldn't the right long-term solution be that
>> NTP provide TAI info?"
>
> NTP can provide leap-second information via an autokey protocol request,
>  see Section 10.6 Leapseconds Values Message (LEAP)
> http://www.ietf.org/internet-drafts/draft-ietf-ntp-autokey-04.txt but

Yes, that look like exactly what would be wanted.  It would be nice
if such a message was available in the regular, non-encrypted protocol.

> that means you need to have autokey set up with another NTP server and
> that means adding infrastructure that you probably don't want and are
> not prepared to handle.

Heh. Yes, well, I still haven't figured out how to secure DNS. Yet clearly
this whole security mess must march on, and somehow the security
infrastructure must eventually become easy to install.

>> Clearly, it would be a lot of work to get the kernel to keep
>> TAI instead of UTC, so this is not, at this time, a "serious
>> proposal".  But if it were possible, and all the various
>> little issues that result were solvable, then it does seem
>> like a better long-term solution.
>>
>
> This is a *lot* more complicated than you might think. If you are
> thinking of implementing this similarly to the way timezone information
> is added for display purposes, you need the whole list of leap seconds
> and when the change happened since you now have to look at a timestamp
> and see when it was and then apply all of the leapseconds up to that
> point in time and none of the leapseconds beyond that. In addition, you
> have legacy files that have UTC timestamps on them so you would need to
> distinguish between UTC (legacy) and TAI timestamps in the file system
> among other places (anywhere where a timestamp exists) and what would
> you do about database tables which contain timestamps? The list goes on.

Yes.

> I'd much rather you spend the time tackling the clock interrupt losses
> that many of our Linux users complain about. See:
> https://support.ntp.org/bin/view/Support/KnownOsIssues#Section_9.2.4.
> for some of the gorier details. I'm sure you don't really want us
> recommending that they set HZ=100 in the kernel to alleviate the problem.

Actually, this is rather sorely lacking in 'gory details', rather, its
a complaint
that 'things don't work' with no discussion of the actual problem.  It would
be much better if there was a link to any previous discussions on LKML on
this issue.

My knee-jerk reaction on reading about the lost-interrupts issue is that,
yes, setting HZ=100 and disabling ACPI is indeed a decent short-term
work-around (APIC is something completely different and not something
you can disable). The correct long-term solution would be to use real-time
kernels, which are designed to make sure that things like lost interrupts
never happen.

I have no idea what the status of real-time Linux is, whether it would now
have gaurantees for timer ticks, and whether anything there would now
be mergeable into the mainline kernel.

--linas
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:45:50 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0578F3A6AD4
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:45:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FYqZZT-x3-L5
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:45:49 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 1B9963A68B2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:45:48 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 9D96A3A017
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:45:33 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 7AF9539F62
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 19:33:38 +0000 (UTC)
	(envelope-from alan@lxorguk.ukuu.org.uk)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 67659-03 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 19:33:17 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 19:33:16 +0000 (UTC)
	(envelope-from alan@lxorguk.ukuu.org.uk)
Received: from lxorguk.ukuu.org.uk (earthlight.etchedpixels.co.uk
	[81.2.110.250])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail2.ntp.org (Postfix) with ESMTP id 910DC398CD
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 19:32:36 +0000 (UTC)
	(envelope-from alan@lxorguk.ukuu.org.uk)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lxorguk.ukuu.org.uk (8.14.2/8.14.2) with ESMTP id n07JVRaK010878;
	Wed, 7 Jan 2009 19:31:27 GMT
Date: Wed, 7 Jan 2009 19:31:27 +0000
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "M. Warner Losh" <imp@bsdimp.com>
Message-ID: <20090107193127.0bec8ad8@lxorguk.ukuu.org.uk>
In-Reply-To: <20090107.103947.1324582654.imp@bsdimp.com>
References: <alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<49642674.9080703@ntp.isc.org>
	<20090107.103947.1324582654.imp@bsdimp.com>
X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.12; x86_64-redhat-linux-gnu)
Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street,
	Windsor, Berkshire, SL4 1TE,
	Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a
	Lloegr o'r rhif cofrestru 3798903
Mime-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:45:07 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	mayer@ntp.isc.org, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	pretzalz@techhouse.org, burdell@iruntheinter.net,
	linasvepstas@gmail.com, nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

> time, causing time to jump backwards by 1s (or violate POSIX time_t's
> invariant that midnight time_t is % 86400 == 0).  This jump backwards
> is a pita in the kernel, and violates the assumption that many
> programs have that time doesn't flow backwards.

They can slew the clock slowly as well. There is a wonderful quote from
one of the summaries of the POSIX committee discussions on time that says
quite simply "the posix clock is not guaranteed to be accurate"

As it currently stands the kernel contains sufficient support that at the
point you know a leap second is coming you can adjust the second length
marginally over the entire period.

The current behaviour is an implementation decision. Jumping on a second
shouldn't be an issue to most people, jumping back is asking for badness
but isn't in fact used in the world today. Slewing the entire day so that
each second is 1/86400 of a second longer or shorter wouldn't be noticed
by anyone.

Alan
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:46:30 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 17EA43A68B2
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:46:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.953
X-Spam-Level: 
X-Spam-Status: No, score=-5.953 tagged_above=-999 required=5
	tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TP2MKRNv2GEg
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:46:29 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 605173A682C
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:46:29 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 46B193A00A
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:46:16 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 05EF439F5E
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 10:57:41 +0000 (UTC)
	(envelope-from alan@lxorguk.ukuu.org.uk)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 61709-08 for <ntpwg@lists.ntp.isc.org>;
	Thu,  8 Jan 2009 10:57:35 +0000 (UTC)
Received: from lxorguk.ukuu.org.uk (earthlight.etchedpixels.co.uk
	[81.2.110.250]) by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 10:56:59 +0000 (UTC)
	(envelope-from alan@lxorguk.ukuu.org.uk)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lxorguk.ukuu.org.uk (8.14.2/8.14.2) with ESMTP id n08AuuKD026737;
	Thu, 8 Jan 2009 10:56:56 GMT
Date: Thu, 8 Jan 2009 10:56:56 +0000
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Message-ID: <20090108105656.6457f6cc@lxorguk.ukuu.org.uk>
In-Reply-To: <20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
References: <20090107.103947.1324582654.imp@bsdimp.com>
	<20090107193127.0bec8ad8@lxorguk.ukuu.org.uk>
	<496579C2.5050800@ntp.isc.org>
	<20090107.214220.-233694826.imp@bsdimp.com>
	<20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.12; x86_64-redhat-linux-gnu)
Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street,
	Windsor, Berkshire, SL4 1TE,
	Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a
	Lloegr o'r rhif cofrestru 3798903
Mime-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:45:08 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	mayer@ntp.isc.org, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	pretzalz@techhouse.org, jeff@kosowsky.org,
	burdell@iruntheinter.net, linasvepstas@gmail.com, nick@nick-andrew.net
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Thu, 8 Jan 2009 10:48:54 +0000
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > On FreeBSD, Solaris and Digital Unix, I'll point out, that jumping
> > backwards is used, and has been used since at least 1994.  So saying
> > it isn't used in the world today is flat out wrong.

[Ignore previous email, must remember not to post before waking up  ;)]

You are correct - and providing gettimeofday() is being used on Linux
rather than time() which simply appears to stall due to resolution the
same is true.

Some users do run with the "right" timezone data in non posix mode
because they want their seconds 'sane' but that isn't the default.

Alan


_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:48:27 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F4063A68B2
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vl7o2Br3wDdX
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:48:26 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id AD6AA3A682C
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:48:26 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id A538839FB0
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:48:13 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id EC29F39F62
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 17:28:35 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 41044-10 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 17:28:20 +0000 (UTC)
X-Greylist: delayed 77651 seconds by postgrey-1.21 at ntp1.isc.org;
	Wed, 07 Jan 2009 17:28:19 UTC
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 17:27:43 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n07HOKc7058556;
	Wed, 7 Jan 2009 10:24:21 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Wed, 07 Jan 2009 10:24:34 -0700 (MST)
Message-Id: <20090107.102434.-1980908153.imp@bsdimp.com>
To: davidn@davidnewall.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <49647E0F.9030008@davidnewall.com>
References: <49642674.9080703@ntp.isc.org>
	<3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
	<49647E0F.9030008@davidnewall.com>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:47:40 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	mayer@ntp.isc.org, linux-kernel@vger.kernel.org,
	ntpwg@lists.ntp.isc.org, pretzalz@techhouse.org,
	burdell@iruntheinter.net, linasvepstas@gmail.com,
	nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message: <49647E0F.9030008@davidnewall.com>
            David Newall <davidn@davidnewall.com> writes:
: Linas Vepstas wrote:
: > Currently, the Linux kernel keeps time in UTC. This means
: > that it must take special actions to tick twice when a leap
: > second comes by.
: 
: Except it doesn't have to tick twice.  Refer to
: http://lkml.org/lkml/2009/1/7/78 in which I show that a time_t (what
: time() returns) counts leap seconds (According to Bernstein this is what
: UTC means), and using zoneinfo, the library processes leap seconds
: correctly.

This is *NOT* POSIX time_t.  In order to be posix compliant, you can't
do what Bernstein suggests.  You can be non-complaint and deal it with
zoneinfo.

: I just realised that the Notes in man 2 time are confusing and probably
: unnecessary.  Suffice to say that (assuming correctly configured
: zoneinfo) time() returns the number of seconds elapsed since start 1970.

That's not POSIX complaint.

Warner
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:49:14 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3D3E3A68D2
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:49:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id W+t7-sWodgtW
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:49:13 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id BECCF3A68B2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:49:13 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id A8B9E39FD9
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:49:00 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 44BE139F62
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 17:39:27 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 58690-01 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 17:39:18 +0000 (UTC)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 17:38:40 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n07HaW9I058707;
	Wed, 7 Jan 2009 10:36:32 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Wed, 07 Jan 2009 10:36:45 -0700 (MST)
Message-Id: <20090107.103645.480811344.imp@bsdimp.com>
To: linasvepstas@gmail.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
References: <3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<49642674.9080703@ntp.isc.org>
	<3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:47:40 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	mayer@ntp.isc.org, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	pretzalz@techhouse.org, burdell@iruntheinter.net,
	nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message: <3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>
            "Linas Vepstas" <linasvepstas@gmail.com> writes:
: However, during the discussion, the idea came out that
: maybe keeping UTC time in the kernel is just plain stupid.
: So there's this idea floating around that maybe the kernel
: should keep TAI time instead. The hope is that this will
: reduce the complexity in the kernel, and push it out to
: user space, "where it belongs" (to repeat a well-worn
: mantra).

I agree that this is where it belongs, but it is hard to do that in a
POSIX compliant way.  It also becomes hard to timestamp things in
filesystems using UTC rather than TAI.  There are other protocols that
deal with UTC times as well.

: However, *if* we were to kick UTC out of the kernel,
: and push it to user-land, then, of course, there's a
: different problem: how does the kernel know what the
: correct TAI time is?  As your reply makes abundantly
: clear, NTP is not a good source for TAI information.

Agreed.  That's the whole crux of the 'multiple time scales suck'
threads that I've talked about in other forums.  You have to know this
information before you start, have to deal with 'dusty system' problem
for systems that have been off for 6 months or not upgraded.  You also
have to cope with learning after the fact that your initial guess was
wrong.

I've had many systems that would get this information from GPS and
stall the rest of the system until this data came in.  I did this
mostly because there were big issues with the software down stream if
you changed the delta between your putative UTC and TAI after the
fact.

: The comments which you labelled as "non-sense" were
: a mis-understanding of  a discussion of a particular issue
: that would arise if the kernel were to keep TAI -- if it did,
: then user-space systems would need to have a reliable
: source for leap-seconds. Since NTP does not
: provide this, there was discussion about how that
: could be worked-around. This then lead to the comment
: that, "gee, wouldn't the right long-term solution be that
: NTP provide TAI info?"

I've wanted this for a long time...

: Clearly, it would be a lot of work to get the kernel to keep
: TAI instead of UTC, so this is not, at this time, a "serious
: proposal".  But if it were possible, and all the various
: little issues that result were solvable, then it does seem
: like a better long-term solution.

Yes.  The kernel would need to be able to return both UTC and TAI
times to the kernel as well, since there are requirements for NFS to
return timestamps in UTC, not in TAI.  Many file systems specify UTC
time, or have traditionally been implemented that way.

Warner
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:49:48 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9F6243A68D2
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vOyaT5adtPGR
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:49:47 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id E37183A68B2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:49:47 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id C704539FE9
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:49:34 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 5013D39F4D
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 17:41:55 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 58689-02 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 17:41:53 +0000 (UTC)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 17:41:53 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n07HdY9N058717;
	Wed, 7 Jan 2009 10:39:34 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Wed, 07 Jan 2009 10:39:47 -0700 (MST)
Message-Id: <20090107.103947.1324582654.imp@bsdimp.com>
To: mayer@ntp.isc.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <49642674.9080703@ntp.isc.org>
References: <alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<49642674.9080703@ntp.isc.org>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:47:40 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	davidn@davidnewall.com, linux-kernel@vger.kernel.org,
	ntpwg@lists.ntp.isc.org, pretzalz@techhouse.org,
	burdell@iruntheinter.net, linasvepstas@gmail.com,
	nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message: <49642674.9080703@ntp.isc.org>
            Danny Mayer <mayer@ntp.isc.org> writes:
: Why don't you tell us what the real problem is instead of telling us
: that you need TAI offset information?

The real problem is that POSIX time_t totally ignores leap seconds.
This forces systems that are rolling through a leap second to repeat
time, causing time to jump backwards by 1s (or violate POSIX time_t's
invariant that midnight time_t is % 86400 == 0).  This jump backwards
is a pita in the kernel, and violates the assumption that many
programs have that time doesn't flow backwards.

The suggestion to solving this would be to tick in TAI time, and force
userland to cope with the leapsecond issues.  Of course, there's a
number of problems with this solution as well, but it feels like it
belongs there...

Warner
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:50:20 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12A513A6A88
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:50:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5S-imncYAcS7
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:50:19 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 3327F3A68E0
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:50:19 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 1E2B039FB9
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:50:06 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id DB49139F62
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 19:46:01 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 68809-04 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 19:45:41 +0000 (UTC)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 19:45:04 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n07JfmHS060129;
	Wed, 7 Jan 2009 12:41:48 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Wed, 07 Jan 2009 12:42:01 -0700 (MST)
Message-Id: <20090107.124201.-1760127186.imp@bsdimp.com>
To: alan@lxorguk.ukuu.org.uk
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20090107193127.0bec8ad8@lxorguk.ukuu.org.uk>
References: <49642674.9080703@ntp.isc.org>
	<20090107.103947.1324582654.imp@bsdimp.com>
	<20090107193127.0bec8ad8@lxorguk.ukuu.org.uk>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:47:40 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	mayer@ntp.isc.org, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	pretzalz@techhouse.org, burdell@iruntheinter.net,
	linasvepstas@gmail.com, nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message: <20090107193127.0bec8ad8@lxorguk.ukuu.org.uk>
            Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
: > time, causing time to jump backwards by 1s (or violate POSIX time_t's
: > invariant that midnight time_t is % 86400 == 0).  This jump backwards
: > is a pita in the kernel, and violates the assumption that many
: > programs have that time doesn't flow backwards.
: 
: They can slew the clock slowly as well. There is a wonderful quote from
: one of the summaries of the POSIX committee discussions on time that says
: quite simply "the posix clock is not guaranteed to be accurate"

True, You can.  However, anybody you peer with via ntpd will have
issues unless things are coordinated with ntpd (and aren't a leaf
node).  There you have much higher tolerances for correctness.

: As it currently stands the kernel contains sufficient support that at the
: point you know a leap second is coming you can adjust the second length
: marginally over the entire period.
: 
: The current behaviour is an implementation decision. Jumping on a second
: shouldn't be an issue to most people, jumping back is asking for badness
: but isn't in fact used in the world today. Slewing the entire day so that
: each second is 1/86400 of a second longer or shorter wouldn't be noticed
: by anyone.

If you are an ntp leaf node, that doesn't care about UTC accurate to
the second, this will work well.  For most users, this effectively
papers over the problem.

If you do care about UTC time being more accurate than this slewing
will be too large and introduce errors that are too big.  Likewise for
non-leaf ntp nodes.  For these machines, having time be off by 1/2
second can be very bad.  There are many real-time systems that fall
into this category, trading systems on wall street, systems that
control things based on doing things at certain points within UTC
second, etc.  For those types of systems, changing the length of the
second by this much isn't going to work at all.

ntpd also lights the INS bit only on 'leap day' so depending on when
you poll, you might not have a full day's notice of these changes, but
that can be managed...

Warner

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:50:42 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB3223A68D2
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:50:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tnT34oOxIUoW
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:50:42 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 18A413A68B2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:50:42 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 0DFA739FEC
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:50:29 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 553F739F24
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 04:45:27 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 12931-06 for <ntpwg@lists.ntp.isc.org>;
	Thu,  8 Jan 2009 04:45:11 +0000 (UTC)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 04:44:36 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n084g758065482;
	Wed, 7 Jan 2009 21:42:07 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Wed, 07 Jan 2009 21:42:20 -0700 (MST)
Message-Id: <20090107.214220.-233694826.imp@bsdimp.com>
To: mayer@ntp.isc.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <496579C2.5050800@ntp.isc.org>
References: <20090107.103947.1324582654.imp@bsdimp.com>
	<20090107193127.0bec8ad8@lxorguk.ukuu.org.uk>
	<496579C2.5050800@ntp.isc.org>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:47:41 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	davidn@davidnewall.com, linux-kernel@vger.kernel.org,
	ntpwg@lists.ntp.isc.org, pretzalz@techhouse.org,
	jeff@kosowsky.org, burdell@iruntheinter.net,
	linasvepstas@gmail.com, nick@nick-andrew.net, alan@lxorguk.ukuu.org.uk
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message: <496579C2.5050800@ntp.isc.org>
            Danny Mayer <mayer@ntp.isc.org> writes:
: Alan Cox wrote:
: >> time, causing time to jump backwards by 1s (or violate POSIX time_t's
: >> invariant that midnight time_t is % 86400 == 0).  This jump backwards
: >> is a pita in the kernel, and violates the assumption that many
: >> programs have that time doesn't flow backwards.
: > 
: > They can slew the clock slowly as well. There is a wonderful quote from
: > one of the summaries of the POSIX committee discussions on time that says
: > quite simply "the posix clock is not guaranteed to be accurate"
: > 
: > As it currently stands the kernel contains sufficient support that at the
: > point you know a leap second is coming you can adjust the second length
: > marginally over the entire period.
: > 
: > The current behaviour is an implementation decision. Jumping on a second
: > shouldn't be an issue to most people, jumping back is asking for badness
: > but isn't in fact used in the world today. Slewing the entire day so that
: > each second is 1/86400 of a second longer or shorter wouldn't be noticed
: > by anyone.
: 
: NTP handles most of this, but it needs the cooperation of the O/S kernel
: and most of the Unix kernels are able to provide the required API's.
: FreeBSD doesn't have any of these problems but Linux historically has.
: Most of that code was designed by Dave Mills but since each kernel is
: different we should not expect them all to behave the same way and
: generally requires an understanding of what NTP expects and that's not
: always clear to kernel developers who are not expected to know NTP.

On FreeBSD, Solaris and Digital Unix, I'll point out, that jumping
backwards is used, and has been used since at least 1994.  So saying
it isn't used in the world today is flat out wrong.

Warner
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:51:04 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE8093A68D2
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:51:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ehFlsJK8Q5Ki
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:51:04 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 2763D3A68B2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:51:04 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 1F87A39F97
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:50:51 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 3730839FA3
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 15:06:22 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 92549-09 for <ntpwg@lists.ntp.isc.org>;
	Thu,  8 Jan 2009 15:06:19 +0000 (UTC)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 15:05:44 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n08F2ETL078283;
	Thu, 8 Jan 2009 08:02:14 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Thu, 08 Jan 2009 08:02:29 -0700 (MST)
Message-Id: <20090108.080229.1159156694.imp@bsdimp.com>
To: alan@lxorguk.ukuu.org.uk
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
References: <496579C2.5050800@ntp.isc.org>
	<20090107.214220.-233694826.imp@bsdimp.com>
	<20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:47:41 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	mayer@ntp.isc.org, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	pretzalz@techhouse.org, burdell@iruntheinter.net,
	linasvepstas@gmail.com, nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message: <20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
            Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
: > On FreeBSD, Solaris and Digital Unix, I'll point out, that jumping
: > backwards is used, and has been used since at least 1994.  So saying
: > it isn't used in the world today is flat out wrong.
: 
: I stand by my comment - when was the last time the IERS used a leap
: second removal ? The code may exist but it doesn't happen.

Jumping backwards is used for every leap second that IERS has ever
done, which was your original comment.  There's has never been a case
where there was a leap second for jump forward though.  The proper
technical term here is 'negative leap second'.  All leap seconds up
until now have been positive leap seconds, and it is unlikely there
ever will be a negative one.

Warner
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:52:08 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 34D273A68D2
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:52:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SsR9x7qoJHgV
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:52:06 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id DB2613A68B2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:52:06 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 6CA4939FE2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:51:53 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 968A739F4F
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 19:24:41 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 67609-03 for <ntpwg@lists.ntp.isc.org>;
	Wed,  7 Jan 2009 19:24:33 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Wed,  7 Jan 2009 19:24:32 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from mail.antoniuk.md (mail.antoniuk.md [65.86.158.146])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail2.ntp.org (Postfix) with ESMTP id E8C9F3990F;
	Wed,  7 Jan 2009 19:24:31 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from [198.22.153.32] (helo=[10.60.98.32])
	by mail.antoniuk.md with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <mayer@ntp.isc.org>)
	id 1LKe0m-0003vh-M5; Wed, 07 Jan 2009 14:24:17 -0500
Message-ID: <4965013F.908@ntp.isc.org>
Date: Wed, 07 Jan 2009 14:23:43 -0500
From: Danny Mayer <mayer@ntp.isc.org>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: linasvepstas@gmail.com
References: <495F0672.6020708@davidnewall.com>	
	<49614835.7000505@davidnewall.com>	
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>	
	<20090105143335.GC18055@mail.local.tull.net>	
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>	
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>	
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>	
	<49642674.9080703@ntp.isc.org>	
	<3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>	
	<4964BD76.9090700@ntp.isc.org>
	<3ae3aa420901070742t8639479qe52cdb615bf46237@mail.gmail.com>
In-Reply-To: <3ae3aa420901070742t8639479qe52cdb615bf46237@mail.gmail.com>
X-kostecke.net-MailScanner: Found to be clean
X-kostecke.net-MailScanner-From: mayer@ntp.isc.org
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:48:25 +0000
Cc: david@lang.hm, Robert Hancock <hancockr@shaw.ca>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>,
	Ben Goodger <goodgerster@gmail.com>, David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	Travis Crump <pretzalz@techhouse.org>, burdell@iruntheinter.net,
	Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mayer@ntp.isc.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Linas Vepstas wrote:
> [...]
> 
>>>   a discussion of a particular issue
>>> that would arise if the kernel were to keep TAI -- if it did,
>>> then user-space systems would need to have a reliable
>>> source for leap-seconds. Since NTP does not
>>> provide this, there was discussion about how that
>>> could be worked-around. This then lead to the comment
>>> that, "gee, wouldn't the right long-term solution be that
>>> NTP provide TAI info?"
>> NTP can provide leap-second information via an autokey protocol request,
>>  see Section 10.6 Leapseconds Values Message (LEAP)
>> http://www.ietf.org/internet-drafts/draft-ietf-ntp-autokey-04.txt but
> 
> Yes, that look like exactly what would be wanted.  It would be nice
> if such a message was available in the regular, non-encrypted protocol.

It's not encrypted, it's an authentication protocol. You really do need
to know that you are receiving a reliable set of information otherwise
anyone can spoof you with bad data and play havoc with your clock and
timestamps.

>> that means you need to have autokey set up with another NTP server and
>> that means adding infrastructure that you probably don't want and are
>> not prepared to handle.
> 
> Heh. Yes, well, I still haven't figured out how to secure DNS. Yet clearly
> this whole security mess must march on, and somehow the security
> infrastructure must eventually become easy to install.
> 
<DNS hat>
That's pretty easy. Install BIND 9.6.0. Read the DNSSEC deployment
instructions here: https://www.isc.org/files/DNSSEC_in_6_minutes.pdf and
implement. You should be done in almost no time.
</DNS hat>

>>> Clearly, it would be a lot of work to get the kernel to keep
>>> TAI instead of UTC, so this is not, at this time, a "serious
>>> proposal".  But if it were possible, and all the various
>>> little issues that result were solvable, then it does seem
>>> like a better long-term solution.
>>>
>> This is a *lot* more complicated than you might think. If you are
>> thinking of implementing this similarly to the way timezone information
>> is added for display purposes, you need the whole list of leap seconds
>> and when the change happened since you now have to look at a timestamp
>> and see when it was and then apply all of the leapseconds up to that
>> point in time and none of the leapseconds beyond that. In addition, you
>> have legacy files that have UTC timestamps on them so you would need to
>> distinguish between UTC (legacy) and TAI timestamps in the file system
>> among other places (anywhere where a timestamp exists) and what would
>> you do about database tables which contain timestamps? The list goes on.
> 
> Yes.
> 
>> I'd much rather you spend the time tackling the clock interrupt losses
>> that many of our Linux users complain about. See:
>> https://support.ntp.org/bin/view/Support/KnownOsIssues#Section_9.2.4.
>> for some of the gorier details. I'm sure you don't really want us
>> recommending that they set HZ=100 in the kernel to alleviate the problem.
> 
> Actually, this is rather sorely lacking in 'gory details', rather, its
> a complaint
> that 'things don't work' with no discussion of the actual problem.  It would
> be much better if there was a link to any previous discussions on LKML on
> this issue.

Sorry, but that's not my area of expertise. I just know we have many
people running Linux and have these issues.

> 
> My knee-jerk reaction on reading about the lost-interrupts issue is that,
> yes, setting HZ=100 and disabling ACPI is indeed a decent short-term
> work-around (APIC is something completely different and not something
> you can disable). The correct long-term solution would be to use real-time
> kernels, which are designed to make sure that things like lost interrupts
> never happen.
> 

I bow to your superior knowledge in this area.

Danny
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 07:52:33 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 789913A68E0
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 07:52:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zicm6AzTwKrN
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 07:52:32 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id B0F273A68B2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 07:52:32 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id A827639FEF
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 15:52:19 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 599F039F6D
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 03:58:12 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 12439-05 for <ntpwg@lists.ntp.isc.org>;
	Thu,  8 Jan 2009 03:58:09 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 03:58:09 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from mail.antoniuk.md (mail.antoniuk.md [65.86.158.146])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail2.ntp.org (Postfix) with ESMTP id A6E1B398AE;
	Thu,  8 Jan 2009 03:58:08 +0000 (UTC)
	(envelope-from mayer@ntp.isc.org)
Received: from cust-63-209-235-219.bos-dynamic.gis.net ([63.209.235.219]
	helo=[10.10.10.101])
	by mail.antoniuk.md with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <mayer@ntp.isc.org>)
	id 1LKm1v-0004fg-9U; Wed, 07 Jan 2009 22:57:59 -0500
Message-ID: <496579C2.5050800@ntp.isc.org>
Date: Wed, 07 Jan 2009 22:57:54 -0500
From: Danny Mayer <mayer@ntp.isc.org>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
References: <alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>	<49642674.9080703@ntp.isc.org>	<20090107.103947.1324582654.imp@bsdimp.com>
	<20090107193127.0bec8ad8@lxorguk.ukuu.org.uk>
In-Reply-To: <20090107193127.0bec8ad8@lxorguk.ukuu.org.uk>
X-kostecke.net-MailScanner: Found to be clean
X-kostecke.net-MailScanner-From: mayer@ntp.isc.org
X-Mailman-Approved-At: Thu, 08 Jan 2009 15:48:25 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	davidn@davidnewall.com, linux-kernel@vger.kernel.org,
	ntpwg@lists.ntp.isc.org, pretzalz@techhouse.org,
	jeff@kosowsky.org, burdell@iruntheinter.net,
	linasvepstas@gmail.com, nick@nick-andrew.net
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mayer@ntp.isc.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Alan Cox wrote:
>> time, causing time to jump backwards by 1s (or violate POSIX time_t's
>> invariant that midnight time_t is % 86400 == 0).  This jump backwards
>> is a pita in the kernel, and violates the assumption that many
>> programs have that time doesn't flow backwards.
> 
> They can slew the clock slowly as well. There is a wonderful quote from
> one of the summaries of the POSIX committee discussions on time that says
> quite simply "the posix clock is not guaranteed to be accurate"
> 
> As it currently stands the kernel contains sufficient support that at the
> point you know a leap second is coming you can adjust the second length
> marginally over the entire period.
> 
> The current behaviour is an implementation decision. Jumping on a second
> shouldn't be an issue to most people, jumping back is asking for badness
> but isn't in fact used in the world today. Slewing the entire day so that
> each second is 1/86400 of a second longer or shorter wouldn't be noticed
> by anyone.

NTP handles most of this, but it needs the cooperation of the O/S kernel
and most of the Unix kernels are able to provide the required API's.
FreeBSD doesn't have any of these problems but Linux historically has.
Most of that code was designed by Dave Mills but since each kernel is
different we should not expect them all to behave the same way and
generally requires an understanding of what NTP expects and that's not
always clear to kernel developers who are not expected to know NTP.

Danny
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Jan  8 14:23:43 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 759C23A6936
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu,  8 Jan 2009 14:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.812
X-Spam-Level: 
X-Spam-Status: No, score=-5.812 tagged_above=-999 required=5
	tests=[AWL=-0.505, BAYES_00=-2.599, MISSING_HEADERS=1.292,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gxex5MjlP0dN
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Thu,  8 Jan 2009 14:23:42 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 5023F3A68A2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 14:23:42 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 5E34A39FE4
	for <ntp-archives-ahFae6za@lists.ietf.org>; Thu,  8 Jan 2009 22:23:28 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id ED27239FE4
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 22:22:58 +0000 (UTC)
	(envelope-from mills@udel.edu)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 47890-09 for <ntpwg@lists.ntp.isc.org>;
	Thu,  8 Jan 2009 22:22:56 +0000 (UTC)
Received: from whimsy.udel.edu (whimsy.udel.edu [128.4.2.3])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 22:22:20 +0000 (UTC)
	(envelope-from mills@udel.edu)
Received: by whimsy.udel.edu (Postfix, from userid 62)
	id 7CBF11C37; Thu,  8 Jan 2009 22:22:19 +0000 (UTC)
Received: from [128.4.2.6] (backroom.udel.edu [128.4.2.6])
	by whimsy.udel.edu (Postfix) with ESMTP id 1C26D1C04;
	Thu,  8 Jan 2009 22:22:15 +0000 (UTC)
Message-ID: <49667C97.10000@udel.edu>
Date: Thu, 08 Jan 2009 22:22:15 +0000
From: David Mills <mills@udel.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
References: <20090107.103947.1324582654.imp@bsdimp.com>	<20090107193127.0bec8ad8@lxorguk.ukuu.org.uk>	<496579C2.5050800@ntp.isc.org>	<20090107.214220.-233694826.imp@bsdimp.com>	<20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
	<20090108105656.6457f6cc@lxorguk.ukuu.org.uk>
In-Reply-To: <20090108105656.6457f6cc@lxorguk.ukuu.org.uk>
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm, v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Cc: ntpwg@lists.ntp.isc.org, linux-kernel@vger.kernel.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Folks,

You are not correct. The kernel software clock variable is in fact 
stepped back, but the routine that actually reads the clock does not 
step the clock back unless set back more than two seconds.. Otherwise, 
the clock is strictly monotonic. That is the ad vice I gave in rfc1583 
and implemented the Digital Unix kernel because I wrote tthe code. Other 
kernelmongers might or might not have taken the advice.

As for the TAI issue discussed earlier, note that the generic NTP kernel 
supportfrom me since 1991  has TAI . However, support to read it 
requires the ntp_gettime()  syscall and nlot all kernels support it.

The recent leap was observed to work correctly in Solaris and FreeBSD. 
It worked fine with the WWV driver and the Spectracom GPS driver, but 
not the NMEA, Arbiter, Meinberg nor any of the NIST or USNO primary 
servers. It probably did work with the Canadian servers, since the 
Ottowa primary server is synchronized via my CHU audio driver. It didn't 
work onn my carefully contrived backroom servers, as they lost power 
durring the event.

See  www.eecis.udel.edu/~mills/leap.html and/or the online NTP 
documentation and/or my book.

Dave

Alan Cox wrote:

>On Thu, 8 Jan 2009 10:48:54 +0000
>Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
>  
>
>>>On FreeBSD, Solaris and Digital Unix, I'll point out, that jumping
>>>backwards is used, and has been used since at least 1994.  So saying
>>>it isn't used in the world today is flat out wrong.
>>>      
>>>
>
>[Ignore previous email, must remember not to post before waking up  ;)]
>
>You are correct - and providing gettimeofday() is being used on Linux
>rather than time() which simply appears to stall due to resolution the
>same is true.
>
>Some users do run with the "right" timezone data in non posix mode
>because they want their seconds 'sane' but that isn't the default.
>
>Alan
>
>
>_______________________________________________
>ntpwg mailing list
>ntpwg@lists.ntp.org
>https://lists.ntp.org/mailman/listinfo/ntpwg
>  
>

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Jan  9 09:00:27 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A91493A6B3C
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Fri,  9 Jan 2009 09:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BFo2-iTRQsWb
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Fri,  9 Jan 2009 09:00:26 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 92BA73A6B3A
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 09:00:26 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 9B24639F8F
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 17:00:11 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 1B73539F7B
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 17:13:33 +0000 (UTC)
	(envelope-from magnus@rubidium.dyndns.org)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 15760-02 for <ntpwg@lists.ntp.isc.org>;
	Thu,  8 Jan 2009 17:13:24 +0000 (UTC)
X-Greylist: delayed 1277 seconds by postgrey-1.21 at ntp1.isc.org;
	Thu, 08 Jan 2009 17:13:24 UTC
Received: from proxy3.bredband.net (proxy3.bredband.net [195.54.101.73])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 17:12:49 +0000 (UTC)
	(envelope-from magnus@rubidium.dyndns.org)
Received: from ironport.bredband.com (195.54.101.120) by proxy3.bredband.net
	(7.3.127) id 492A9CFF00F72730 for ntpwg@lists.ntp.isc.org;
	Thu, 8 Jan 2009 17:51:30 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiI3AIi9ZUlT46GbPGdsb2JhbACUBgEBAQEeFwu6bYV1
Received: from ua-83-227-161-155.cust.bredbandsbolaget.se (HELO magda-gw)
	([83.227.161.155])
	by ironport1.bredband.com with ESMTP; 08 Jan 2009 17:51:29 +0100
Received: from magda-gw (localhost [127.0.0.1])
	by magda-gw (Postfix) with ESMTP id B5D341B6EA;
	Thu,  8 Jan 2009 17:51:28 +0100 (CET)
Received: by magda-gw (Postfix, from userid 1000)
	id 61D8D1B733; Thu,  8 Jan 2009 17:51:28 +0100 (CET)
Received: from [192.168.0.3] (heaven [192.168.0.3])
	by magda-gw (Postfix) with ESMTP id 22FD11B6EA;
	Thu,  8 Jan 2009 17:51:20 +0100 (CET)
Message-ID: <49662F08.4070607@rubidium.dyndns.org>
Date: Thu, 08 Jan 2009 17:51:20 +0100
From: Magnus Danielson <magnus@rubidium.dyndns.org>
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: "M. Warner Losh" <imp@bsdimp.com>
References: <49642674.9080703@ntp.isc.org>	<3ae3aa420901062052h75fcab11n8ce45c41ac0e4cd2@mail.gmail.com>	<49647E0F.9030008@davidnewall.com>
	<20090107.102434.-1980908153.imp@bsdimp.com>
In-Reply-To: <20090107.102434.-1980908153.imp@bsdimp.com>
X-Virus-Scanned: ClamAV using ClamSMTP
X-Mailman-Approved-At: Fri, 09 Jan 2009 16:59:40 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	magnus@rubidium.dyndns.org, slashdot@jameshallam.info,
	goodgerster@gmail.com, mayer@ntp.isc.org, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	pretzalz@techhouse.org, burdell@iruntheinter.net,
	linasvepstas@gmail.com, nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

M. Warner Losh skrev:
> In message: <49647E0F.9030008@davidnewall.com>
>             David Newall <davidn@davidnewall.com> writes:
> : Linas Vepstas wrote:
> : > Currently, the Linux kernel keeps time in UTC. This means
> : > that it must take special actions to tick twice when a leap
> : > second comes by.
> : 
> : Except it doesn't have to tick twice.  Refer to
> : http://lkml.org/lkml/2009/1/7/78 in which I show that a time_t (what
> : time() returns) counts leap seconds (According to Bernstein this is what
> : UTC means), and using zoneinfo, the library processes leap seconds
> : correctly.
> 
> This is *NOT* POSIX time_t.  In order to be posix compliant, you can't
> do what Bernstein suggests.  You can be non-complaint and deal it with
> zoneinfo.

You are free to keep your core time in whatever form you wish, but if 
you want your time_t to be POSIX compatible when accessed over POSIX 
interfaces you would need to honour the POSIX time_t mapping. While 
POSIX tried to avoid the leapsecond issue, the mapping they do perform 
has a peculiar effect on what happends on time_t if you also want to 
honour the UTC to time_t mapping while accepting UTC from external sources.

> : I just realised that the Notes in man 2 time are confusing and probably
> : unnecessary.  Suffice to say that (assuming correctly configured
> : zoneinfo) time() returns the number of seconds elapsed since start 1970.
> 
> That's not POSIX complaint.

It just *appears* to be the number of "seconds" since 1970. This 
appearence is important to some and causing a greif to others.

Cheers,
Magnus
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Jan  9 09:02:54 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DC9D3A6881
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Fri,  9 Jan 2009 09:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MJ0lIWa0OpD5
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Fri,  9 Jan 2009 09:02:53 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id A33923A6784
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 09:02:50 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 5D6CC39FBB
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 17:02:37 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 0DA4839FC5
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 20:11:02 +0000 (UTC)
	(envelope-from sla@ucolick.org)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 35009-09 for <ntpwg@lists.ntp.isc.org>;
	Thu,  8 Jan 2009 20:10:55 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 20:10:55 +0000 (UTC)
	(envelope-from sla@ucolick.org)
Received: from smtp.ucolick.org (zilan.ucolick.org [128.114.23.234])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail2.ntp.org (Postfix) with ESMTP id A0F4E398FF
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 20:10:16 +0000 (UTC)
	(envelope-from sla@ucolick.org)
Received: from smtp.ucolick.org (localhost [127.0.0.1])
	by smtp.ucolick.org (Postfix) with ESMTP id 096E316D6;
	Thu,  8 Jan 2009 12:09:39 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.ucolick.org (Postfix) with ESMTP id CDB8F275C;
	Thu,  8 Jan 2009 12:09:38 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1])
	by geneva.ucolick.org (8.13.8/8.13.8) with ESMTP id n08K9cwA018964;
	Thu, 8 Jan 2009 12:09:38 -0800
Received: (from sla@localhost)
	by geneva.ucolick.org (8.13.8/8.13.8/Submit) id n08K9Yuw018963;
	Thu, 8 Jan 2009 12:09:34 -0800
Date: Thu, 8 Jan 2009 12:09:34 -0800
From: Steve Allen <sla@ucolick.org>
To: "M. Warner Losh" <imp@bsdimp.com>
Message-ID: <20090108200934.GA18773@ucolick.org>
References: <alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<49642674.9080703@ntp.isc.org>
	<20090107.103947.1324582654.imp@bsdimp.com>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20090107.103947.1324582654.imp@bsdimp.com>
User-Agent: Mutt/1.4.2.2i
X-Mailman-Approved-At: Fri, 09 Jan 2009 17:02:05 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	mayer@ntp.isc.org, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	pretzalz@techhouse.org, burdell@iruntheinter.net,
	linasvepstas@gmail.com, nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Leap Second Discussion List <leapsecs@leapsecond.com>
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Wed 2009-01-07T10:39:47 -0700, M. Warner Losh hath writ:
> The suggestion to solving this would be to tick in TAI time, and force
> userland to cope with the leapsecond issues.  Of course, there's a
> number of problems with this solution as well, but it feels like it
> belongs there...

Agreed that the leap second belong in userland, but BIPM itself
refuses to agree with the idea of the underlying time scale being TAI.
TAI has no standing as an international recommendation, and it is not
available via the established broadcast mechanisms, and BIPM does not
want those things to happen.  What would be needed is a leap-free time
scale with an international recommendation standing behind it so as to
legitimize its use.

The most recent public insight to the ITU-R process of reconsidering
leap seconds in UTC is from September, here
http://www.navcen.uscg.gov/cgsic/meetings/48thmeeting/Reports/Timing%20Subcommittee/48-LS%2020080916.pdf
In the schedule given on page 16 we see that even if the ITU-R process
goes smoothly there will be leap seconds at least until 2017, so we
have to live with them for at least that long.  However, at the
October meeting of ITU-R WP7A things did not go smoothly.  There were
two countries objecting to any change to UTC, so the process of
considering any change to the broadcast time scale is stalled.

Basically, any change to UTC is currently stalled by the
international political/diplomatic process which controls it.

Way back in 2003 the ITU-R asked for advice on the broadcast time
scale, and the advice from the experts included changing the name if
leaps are dropped.
http://www.inrim.it/luc/cesio/itu/closure.pdf
At that point nobody managed to point out that POSIX demands that the
zoneinfo mechanisms allow for offsets of seconds as well as minutes,
so there was no clear path for implementing that advice while
preserving compliance with specifications that still demand UTC.

Any epoch-based time scale has issues with UTC as it has been defined
http://www.ucolick.org/~sla/leapsecs/epochtime.html
and by ignoring leap seconds POSIX makes that even harder to implement.
During the past century we have seen the creation of at least 4
different uniform time scales, two of which are widely available by
broacast (LORAN-C and GPS), but none of which has the backing of an
international standard behind it.
http://www.ucolick.org/~sla/leapsecs/deltat.html

All civil time scales are conventional constructs, and zoneinfo is
designed to handle the arbitrary nature of changes to civil time.  If
the underlying time scale changes its name and stops having leaps,
then leap seconds in UTC are just another form of conventional change
to civil time.  UTC could become a time zone.  Processes which happen
when POSIX time_t % 86400 == 0 would happen at "atomic midnight"
instead of "civil" midnight, not a big difference.

If the ITU-R were to take the advice of the colloquium it organized,
if they were to abandon the name UTC, and establish a new
international broadcast time scale with a new name, then the
operational systems of the world receiving those broadcasts would not
notice.  There would be some rewriting of documents, specifications,
and some extra work streamlining zoneinfo.

It's not just an engineering tradeoff, it's a political tradeoff.
The question for the NTP implementors, kernel hackers, application
writers is whether it's worth waiting to see if the current political
impasse about UTC can be broken, or whether it seems better, easier,
and quicker to lobby the ITU-R delegations to abandon the name UTC
and give a new name to a broadcast time scale without leaps.

Either way we will have to handle another decade of leap seconds
before the broadcast time scale can change its characteristics.

replies directed to the LEAPSECS list

--
Steve Allen                 <sla@ucolick.org>                WGS-84 (GPS)
UCO/Lick Observatory        Natural Sciences II, Room 165    Lat  +36.99855
University of California    Voice: +1 831 459 3046           Lng -122.06015
Santa Cruz, CA 95064        http://www.ucolick.org/~sla/     Hgt +250 m
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Jan  9 09:04:09 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B48E73A6784
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Fri,  9 Jan 2009 09:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.855
X-Spam-Level: 
X-Spam-Status: No, score=-104.855 tagged_above=-999 required=5
	tests=[AWL=1.744, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tPFFkJVsZIhb
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Fri,  9 Jan 2009 09:04:08 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id AD8003A69D7
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 09:04:08 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id D3D0D39F98
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 17:03:54 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 8418239F24
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 19:58:44 +0000 (UTC)
	(envelope-from tme@multicasttech.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 36236-06 for <ntpwg@lists.ntp.isc.org>;
	Thu,  8 Jan 2009 19:58:02 +0000 (UTC)
X-Greylist: delayed 3597 seconds by postgrey-1.21 at ntp1.isc.org;
	Thu, 08 Jan 2009 19:58:01 UTC
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Thu,  8 Jan 2009 19:57:25 +0000 (UTC)
	(envelope-from tme@multicasttech.com)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1])
	by multicasttech.com (CommuniGate Pro SMTP 3.4.8)
	with ESMTP-TLS id 14199335; Thu, 08 Jan 2009 13:57:25 -0500
Message-Id: <9981A902-73ED-44B9-87B5-803621BF307B@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20090108.080229.1159156694.imp@bsdimp.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 8 Jan 2009 13:57:24 -0500
References: <496579C2.5050800@ntp.isc.org>
	<20090107.214220.-233694826.imp@bsdimp.com>
	<20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
	<20090108.080229.1159156694.imp@bsdimp.com>
X-Mailer: Apple Mail (2.930.3)
X-Mailman-Approved-At: Fri, 09 Jan 2009 17:03:18 +0000
Cc: david@lang.hm, hancockr@shaw.ca, kyle@moffetthome.net,
	slashdot@jameshallam.info, goodgerster@gmail.com,
	mayer@ntp.isc.org, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, ntpwg@lists.ntp.isc.org,
	pretzalz@techhouse.org, jeff@kosowsky.org,
	burdell@iruntheinter.net, linasvepstas@gmail.com,
	nick@nick-andrew.net, alan@lxorguk.ukuu.org.uk
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org


On Jan 8, 2009, at 10:02 AM, M. Warner Losh wrote:

> In message: <20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
>            Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> : > On FreeBSD, Solaris and Digital Unix, I'll point out, that jumping
> : > backwards is used, and has been used since at least 1994.  So  
> saying
> : > it isn't used in the world today is flat out wrong.
> :
> : I stand by my comment - when was the last time the IERS used a leap
> : second removal ? The code may exist but it doesn't happen.
>
> Jumping backwards is used for every leap second that IERS has ever
> done, which was your original comment.  There's has never been a case
> where there was a leap second for jump forward though.  The proper
> technical term here is 'negative leap second'.  All leap seconds up
> until now have been positive leap seconds, and it is unlikely there
> ever will be a negative one.

I disagree. In the 1970's, the excess LOD was as much as 3 msec.
After going down some, the mid 1990's it rose to around 2 msec.
Now, it is around 1 msec.

Here is a plot

http://www.iers.org/MainDisp.csl?pid=95-100

Only the long period variations count for leap seconds - the seasonal  
and other high frequency
oscillations tend to average out.

In the early part of the last century (~1905), it decreased by ~ 5  
msec in a year or so.
If that happened right now, it would go to ~ -4 msec negative, and we  
would be seeing
2 negative leap seconds or more per year. Even if the decrease from  
1975 to 1985 happened again, it
would be at -1 msec, and we would have a negative leap second every  
two years or so.

What is a reasonable assumption is that we would likely have a year or  
more warning of the
likelihood of a negative leap second.

Regards
Marshall Eubanks

>
>
> Warner
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> https://lists.ntp.org/mailman/listinfo/ntpwg

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Jan  9 09:24:06 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 31ABB3A6850
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Fri,  9 Jan 2009 09:24:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.872
X-Spam-Level: 
X-Spam-Status: No, score=-104.872 tagged_above=-999 required=5
	tests=[AWL=1.727, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kp+A0+2Yz3-n
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Fri,  9 Jan 2009 09:24:05 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 372183A67EE
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 09:24:05 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id E50F639FAF
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 17:23:51 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 6FB7739F67
	for <ntpwg@lists.ntp.isc.org>; Fri,  9 Jan 2009 17:23:27 +0000 (UTC)
	(envelope-from tme@multicasttech.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 81873-08 for <ntpwg@lists.ntp.isc.org>;
	Fri,  9 Jan 2009 17:22:35 +0000 (UTC)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Fri,  9 Jan 2009 17:21:59 +0000 (UTC)
	(envelope-from tme@multicasttech.com)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1])
	by multicasttech.com (CommuniGate Pro SMTP 3.4.8)
	with ESMTP-TLS id 14206899; Fri, 09 Jan 2009 12:21:59 -0500
Message-Id: <EBD0BA99-3BE1-487D-B011-E0DB42755C86@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20090108.080229.1159156694.imp@bsdimp.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 9 Jan 2009 12:21:58 -0500
References: <496579C2.5050800@ntp.isc.org>
	<20090107.214220.-233694826.imp@bsdimp.com>
	<20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
	<20090108.080229.1159156694.imp@bsdimp.com>
X-Mailer: Apple Mail (2.930.3)
Cc: ntpwg@lists.ntp.isc.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org


On Jan 8, 2009, at 10:02 AM, M. Warner Losh wrote:

> In message: <20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
>           Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> : > On FreeBSD, Solaris and Digital Unix, I'll point out, that jumping
> : > backwards is used, and has been used since at least 1994.  So  
> saying
> : > it isn't used in the world today is flat out wrong.
> :
> : I stand by my comment - when was the last time the IERS used a leap
> : second removal ? The code may exist but it doesn't happen.
>
> Jumping backwards is used for every leap second that IERS has ever
> done, which was your original comment.  There's has never been a case
> where there was a leap second for jump forward though.  The proper
> technical term here is 'negative leap second'.  All leap seconds up
> until now have been positive leap seconds, and it is unlikely there
> ever will be a negative one.

I disagree. In the 1970's, the excess LOD was as much as 3 msec.
After going down some, the mid 1990's it rose to around 2 msec.
Now, it is around 1 msec.

Here is a plot

http://www.iers.org/MainDisp.csl?pid=95-100

Only the long period variations count for leap seconds - the seasonal  
and other high frequency
oscillations tend to average out.

In the early part of the last century (~1905), it decreased by ~ 5  
msec in a year or so.
If that happened right now, it would go to ~ -4 msec negative, and we  
would be seeing
2 negative leap seconds or more per year. Even if the decrease from  
1975 to 1985 happened again, it
would be at -1 msec, and we would have a negative leap second every  
two years or so.

What is a reasonable assumption is that we would likely have a year or  
more warning of the
likelihood of a negative leap second.

Regards
Marshall Eubanks

>
>
> Warner
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> https://lists.ntp.org/mailman/listinfo/ntpwg

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Jan  9 13:29:09 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5FB443A68DC
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Fri,  9 Jan 2009 13:29:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aI4eoP-deoXg
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Fri,  9 Jan 2009 13:29:08 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 6CB883A67EE
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 13:29:08 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 39EA83A001
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 21:28:54 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 73BE339F7D
	for <ntpwg@lists.ntp.org>; Fri,  9 Jan 2009 21:28:28 +0000 (UTC)
	(envelope-from stuart.venters@adtran.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 26287-01 for <ntpwg@lists.ntp.org>;
	Fri,  9 Jan 2009 21:28:14 +0000 (UTC)
X-Greylist: delayed 3426 seconds by postgrey-1.21 at ntp1.isc.org;
	Fri, 09 Jan 2009 21:28:14 UTC
Received: from p02c12o144.mxlogic.net (p02c12o144.mxlogic.net [208.65.145.77])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.org>; Fri,  9 Jan 2009 21:27:38 +0000 (UTC)
	(envelope-from stuart.venters@adtran.com)
Received: from unknown [208.251.151.99] (EHLO p02c12o144.mxlogic.net)
	by p02c12o144.mxlogic.net (mxl_mta-6.1.0-1)
	with ESMTP id a41c7694.2755267472.91614.00-590.p02c12o144.mxlogic.net
	(envelope-from <stuart.venters@adtran.com>); 
	Fri, 09 Jan 2009 14:28:15 -0700 (MST)
Received: from unknown [208.251.151.99]
	by p02c12o144.mxlogic.net (mxl_mta-6.1.0-1)
	with SMTP id 5e3b7694.2944084880.76187.00-098.p02c12o144.mxlogic.net
	(envelope-from <stuart.venters@adtran.com>); 
	Fri, 09 Jan 2009 13:31:00 -0700 (MST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 9 Jan 2009 14:29:36 -0600
Message-ID: <8F242B230AD6474C8E7815DE0B4982D70B99D634@EXV1.corp.adtran.com>
In-Reply-To: <mailman.2908.1231429688.18773.ntpwg@lists.ntp.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ntpwg Digest, Vol 46, Issue 4
Thread-Index: AclxqR5ZDyGVVMkURLeMnSk0VHOmmQA7ilFQ
From: "STUART VENTERS" <stuart.venters@adtran.com>
To: <ntpwg@lists.ntp.org>
X-Spam: [F=0.2000000000; S=0.200(2008120801)]
X-MAIL-FROM: <stuart.venters@adtran.com>
X-SOURCE-IP: [208.251.151.99]
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org


> time, causing time to jump backwards by 1s (or violate POSIX time_t's
> invariant that midnight time_t is % 86400 == 0).  This jump backwards
> is a pita in the kernel, and violates the assumption that many
> programs have that time doesn't flow backwards.

If the kernel is going to keep legal time (which seems to come with leap seconds), 
then many applications might be better off getting suspended for a second if they happen to ask for the time during a leap second.  At least then the app wouldn't see any violations of the Posix spec.

I guess the applications that aren't better off are the one that keep the
kernel from just hanging for a second to let the earth catch up.


Cheers,

Stuart


----------------------------------------------------------------------
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Jan  9 14:28:15 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C28053A697D
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Fri,  9 Jan 2009 14:28:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NwCHMeDetmP2
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Fri,  9 Jan 2009 14:28:14 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 1EE813A6893
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 14:28:14 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 8F8A839FE2
	for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  9 Jan 2009 22:28:00 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 4E9A539F55
	for <ntpwg@lists.ntp.isc.org>; Fri,  9 Jan 2009 22:27:23 +0000 (UTC)
	(envelope-from seaman@noao.edu)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 21894-07 for <ntpwg@lists.ntp.isc.org>;
	Fri,  9 Jan 2009 22:27:13 +0000 (UTC)
X-Greylist: delayed 3635 seconds by postgrey-1.21 at ntp1.isc.org;
	Fri, 09 Jan 2009 22:27:12 UTC
Received: from noao.edu (noao.edu [140.252.1.54])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Fri,  9 Jan 2009 22:26:37 +0000 (UTC)
	(envelope-from seaman@noao.edu)
Received: from baleen.tuc.noao.edu ([140.252.4.27] verified)
	by noao.edu (CommuniGate Pro SMTP 5.2.10)
	with ESMTPS id 65615239; Fri, 09 Jan 2009 14:26:01 -0700
Message-Id: <05D2F2A0-5526-41EB-80A9-8D48A4D450A2@noao.edu>
From: Rob Seaman <seaman@noao.edu>
To: ntpwg@lists.ntp.isc.org
In-Reply-To: <9743C22F-5316-41BC-B748-B0662696C9B5@noao.edu>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 9 Jan 2009 14:26:00 -0700
References: <496579C2.5050800@ntp.isc.org>
	<20090107.214220.-233694826.imp@bsdimp.com>
	<20090108104854.2dbc41b1@lxorguk.ukuu.org.uk>
	<20090108.080229.1159156694.imp@bsdimp.com>
	<EBD0BA99-3BE1-487D-B011-E0DB42755C86@multicasttech.com>
	<A8532B03-BA72-49FC-849F-2FC1F8E19FA6@noao.edu>
	<9743C22F-5316-41BC-B748-B0662696C9B5@noao.edu>
X-Mailer: Apple Mail (2.930.3)
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0989415119=="
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org


--===============0989415119==
Content-Type: multipart/alternative; boundary=Apple-Mail-58--173909737


--Apple-Mail-58--173909737
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Follow-ups to leapsecs@leapsecond.com.

Marshall Eubanks wrote:

> I disagree. In the 1970's, the excess LOD was as much as 3 msec.   
> After going down some, the mid 1990's it rose to around 2 msec.   
> Now, it is around 1 msec.
>
> Here is a plot
>
> http://www.iers.org/MainDisp.csl?pid=95-100
>
> Only the long period variations count for leap seconds - the  
> seasonal and other high frequency oscillations tend to average out.

Those plots are almost a decade out of date.  The more recent trend is  
here:

	http://tycho.usno.navy.mil/leapsec.html

Obviously we already knew it had leveled off (even risen a little) in  
the last few years since we've had two leap seconds in three years.

> In the early part of the last century (~1905), it decreased by ~ 5  
> msec in a year or so.  If that happened right now, it would go to ~  
> -4 msec negative, and we would be seeing 2 negative leap seconds or  
> more per year.

What am I missing here?  Wasn't the episode near 1905 first a big  
deceleration before it returned to "normal"?  A slower Earth leads to  
an additional accumulation of positive leap seconds.  Here's a plot  
from Steve Allen's page that shows the large positive area under the  
curve for the 1905 event:

	http://www.ucolick.org/~sla/leapsecs/lod.png

It looks like the fall took more like 2 decades than "a year or so",  
and that the initial rise was significantly steeper.

Perhaps the USNO or IERS has some other view of this event?  References?

> Even if the decrease from 1975 to 1985 happened again, it would be  
> at -1 msec, and we would have a negative leap second every two years  
> or so.

It depends what the baseline is doing before such a decrease.  Which  
is just to say, I guess, that length of day is not well modeled by a  
Markov process.

> What is a reasonable assumption is that we would likely have a year  
> or  more warning of the likelihood of a negative leap second.

Yes, but why is this left as an assumption?  As the result of  
integrating the LOD curve, leap seconds are stabilized relative to the  
variations in the curve itself.  Figure 5 from the Arias, et.al. paper  
from Torino:

	http://www.ucolick.org/~sla/leapsecs/torino/arias_3.pdf

suggests that predictions as long as three years should be possible  
even using what seems from the paper to be a fairly simple minded  
approach.  Since the Bulletin A methodology has presumably been  
optimized for six month predictions, it seems likely this could be  
extended by a year or two even without relaxing the DUT1 < 0.9s limit.

Figure 4 from Arias shows residual baseline trends extending over  
several six month windows.  A purely phenomenological detrending might  
behave better in practice than some attempt at unbiased fitting of  
physical models.

Leap seconds are an engineering issue, not science - a thumb on the  
scale isn't out of the question.

Rob Seaman
National Optical Astronomy Observatory



--Apple-Mail-58--173909737
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div>Follow-ups to&nbsp;<a =
href=3D"mailto:leapsecs@leapsecond.com">leapsecs@leapsecond.com</a>.</div>=
<div><br></div><div>Marshall Eubanks wrote:<br><br><blockquote =
type=3D"cite">I disagree. In the 1970's, the excess LOD was as much as 3 =
msec. &nbsp;After going down some, the mid 1990's it rose to around 2 =
msec. &nbsp;Now, it is around 1 msec.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Here is a =
plot<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"http://www.iers.org/MainDisp.csl?pid=3D95-100">http://www.iers.org=
/MainDisp.csl?pid=3D95-100</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Only the long =
period variations count for leap seconds - the seasonal&nbsp;<span =
class=3D"Apple-style-span" style=3D"-webkit-text-stroke-width: -1; ">and =
other high frequency oscillations tend to average =
out.</span></blockquote><div><br></div>Those plots are almost a decade =
out of date. &nbsp;The more recent trend is here:<br><br><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span><a =
href=3D"http://tycho.usno.navy.mil/leapsec.html">http://tycho.usno.navy.mi=
l/leapsec.html</a></div><div><br></div><div>Obviously we already knew it =
had leveled off (even risen a little) in the last few years since we've =
had two leap seconds in three years.</div><div><br><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"-webkit-text-stroke-width: -1; ">In the early part of the last =
century (~1905), it decreased by ~ 5 msec in a year or so. &nbsp;If that =
happened right now, it would go to ~ -4 msec negative, and we would be =
seeing 2 negative leap seconds or more per =
year.</span></blockquote><div><br></div>What am I missing here? =
&nbsp;Wasn't the episode near 1905 first a big deceleration before it =
returned to "normal"? &nbsp;A slower Earth leads to an additional =
accumulation of positive leap seconds. &nbsp;Here's a plot from Steve =
Allen's page that shows the large positive area under the curve for the =
1905 event:</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><a =
href=3D"http://www.ucolick.org/~sla/leapsecs/lod.png">http://www.ucolick.o=
rg/~sla/leapsecs/lod.png</a></div><div><br></div><div>It looks like the =
fall took more like 2 decades than "a year or so", and that the initial =
rise was significantly steeper.</div><div><br></div><div>Perhaps the =
USNO or IERS has some other view of this event? =
&nbsp;References?<br><div><br></div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"-webkit-text-stroke-width: -1; =
">Even if the decrease from 1975 to 1985 happened again, it would be at =
-1 msec, and we would have a negative leap second every two years or =
so.</span></blockquote><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"-webkit-text-stroke-width: -1; =
"></span></blockquote><br><span class=3D"Apple-style-span" =
style=3D"-webkit-text-stroke-width: -1; ">It depends what the baseline =
is doing before such a decrease. &nbsp;Which is just to say, I guess, =
that length of day is not well modeled by a Markov =
process.</span></div><div><br></div><div><blockquote type=3D"cite">What =
is a reasonable assumption is that we would likely have a year or =
&nbsp;more warning of the likelihood of a negative leap =
second.<br></blockquote><div><br></div>Yes, but why is this left as an =
assumption? &nbsp;As the result of integrating the LOD curve, leap =
seconds are stabilized relative to the variations in the curve itself. =
&nbsp;Figure 5 from the Arias, et.al. paper from =
Torino:</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><a =
href=3D"http://www.ucolick.org/~sla/leapsecs/torino/arias_3.pdf">http://ww=
w.ucolick.org/~sla/leapsecs/torino/arias_3.pdf</a></div><div><br></div><di=
v>suggests that predictions as long as three years should be possible =
even using what seems from the paper to be a fairly simple minded =
approach. &nbsp;Since the Bulletin A methodology has presumably been =
optimized for six month predictions, it seems likely this could be =
extended by a year or two even without relaxing the DUT1 &lt; 0.9s =
limit.</div><div><br></div><div>Figure 4 from Arias shows residual =
baseline trends extending over several six month windows. &nbsp;A purely =
phenomenological detrending might behave better in practice than some =
attempt at unbiased fitting of physical =
models.</div><div><br></div><div>Leap seconds are an engineering issue, =
not science - a thumb on the scale isn't out of the =
question.<br><div><font class=3D"Apple-style-span" =
color=3D"#144FAE"><br></font></div>Rob Seaman<br>National Optical =
Astronomy Observatory<br></div></div><br></div></div><br></body></html>=

--Apple-Mail-58--173909737--

--===============0989415119==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg
--===============0989415119==--


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Jan 12 08:56:14 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B2E9E28C32A
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Mon, 12 Jan 2009 08:56:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cD+yWH45q08q
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Mon, 12 Jan 2009 08:56:13 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id A492D28C329
	for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 12 Jan 2009 08:56:13 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id F13A239F7A
	for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 12 Jan 2009 16:55:58 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 4D6C339F63
	for <ntpwg@lists.ntp.isc.org>; Mon, 12 Jan 2009 16:13:10 +0000 (UTC)
	(envelope-from pavel@ucw.cz)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 80717-08 for <ntpwg@lists.ntp.isc.org>;
	Mon, 12 Jan 2009 16:12:54 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Mon, 12 Jan 2009 16:12:52 +0000 (UTC)
	(envelope-from pavel@ucw.cz)
Received: from gprs189-60.eurotel.cz (gprs189-60.eurotel.cz [160.218.189.60])
	by mail2.ntp.org (Postfix) with ESMTP id 822ED398CD
	for <ntpwg@lists.ntp.isc.org>; Mon, 12 Jan 2009 16:12:09 +0000 (UTC)
	(envelope-from pavel@ucw.cz)
Received: by gprs189-60.eurotel.cz (Postfix, from userid 1001)
	id 7973C11FD1; Mon, 12 Jan 2009 17:11:16 +0100 (CET)
Date: Mon, 12 Jan 2009 17:11:15 +0100
From: Pavel Machek <pavel@suse.cz>
To: Linas Vepstas <linasvepstas@gmail.com>
Message-ID: <20090112161115.GA1474@ucw.cz>
References: <4960897D.5030603@davidnewall.com>
	<alpine.DEB.1.10.0901040310070.24563@asgard.lang.hm>
	<4961432A.80509@davidnewall.com>
	<alpine.DEB.1.10.0901041628100.25545@asgard.lang.hm>
	<49614835.7000505@davidnewall.com>
	<3ae3aa420901042148o1c96985dube8e03085c997a07@mail.gmail.com>
	<20090105143335.GC18055@mail.local.tull.net>
	<3ae3aa420901050808r100e533fo5f88edfbb5f0747a@mail.gmail.com>
	<alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Mailman-Approved-At: Mon, 12 Jan 2009 16:55:31 +0000
Cc: david@lang.hm, Ben Goodger <goodgerster@gmail.com>,
	Kyle Moffett <kyle@moffetthome.net>,
	MentalMooMan <slashdot@jameshallam.info>,
	David Newall <davidn@davidnewall.com>,
	linux-kernel@vger.kernel.org, Robert Hancock <hancockr@shaw.ca>,
	ntpwg@lists.ntp.isc.org, Travis Crump <pretzalz@techhouse.org>,
	burdell@iruntheinter.net, Nick Andrew <nick@nick-andrew.net>,
	"Jeffrey J. Kosowsky" <jeff@kosowsky.org>
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years	2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Mon 2009-01-05 11:42:35, Linas Vepstas wrote:
> 2009/1/5  <david@lang.hm>:
> > On Mon, 5 Jan 2009, Linas Vepstas wrote:
> >
> >>> Arguably the kernel's responsibility should be to keep track of the
> >>> most fundamental representation of time possible for a machine (that's
> >>> probably TAI) and it is a userspace responsibility to map from that
> >>> value to other time standards including UTC,
> >>
> >> Yes, this really does seem like the right solution.
> >>
> >>> using control files
> >>> which are updated as leap seconds are declared.
> >>
> >> Lets be clear on what "control files" means.  This does
> >> *NOT* mean some config file shipped by some distro
> >> for some package. That would be a horrid solution.
> >> People don't install updates, patches, etc.  Distros
> >> ship them late, or never, if the distro is old enough.
> >>
> >> A more appropriate solution would be to have
> >> either the kernel or ntpd track the leap seconds
> >> automatically.  First, the ntp protocol already provides
> >> the needed notification of a leap second to anyone
> >> who cares about it (i.e. there is no point in getting a
> >> Linux distro involved in this -- a distribution mechanism
> >> already exists, and works *better* than having a distro
> >> do it).
> >
> > I disagree with this. NTP will only know about leap seconds if it was
> > running and connected to a server that advertised the leap seconds during
> > that month.
> >
> > for example, if you installed a new server today, how would it ever know
> > that there was a leap second a couple of days ago?
> 
> OK, good point.  Unless your distro was less
> than a few days old (unlikely), you are faced with the
> same problem.  Sure, eventually, the distro will publish
> an update (which will add to the existing list of 36 leap
> seconds -- which is needed in any case, since no one
> has a server that's been up since 1958),  but this is
> unlikely to happen during this install window.
> 
> The long term solution would be write an RFC to extend
> NTP to also provide TAI information -- e.g. to add a
> message that indicates the current leap-second offset
> between UTC and TAI.

Offset is not enough; you'd have to provide list of all previous leap
seconds with 'when it happened' timestamps.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Jan 13 07:38:09 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C962C3A67FF
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Tue, 13 Jan 2009 07:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VoqsS9M6qd5j
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Tue, 13 Jan 2009 07:38:08 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id B60813A6920
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 13 Jan 2009 07:38:08 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 3844739FB3
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 13 Jan 2009 15:37:53 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 93E8339F67
	for <ntpwg@lists.ntp.isc.org>; Mon, 12 Jan 2009 17:09:44 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 95079-03 for <ntpwg@lists.ntp.isc.org>;
	Mon, 12 Jan 2009 17:09:38 +0000 (UTC)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Mon, 12 Jan 2009 17:09:00 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n0CH6ofj069806;
	Mon, 12 Jan 2009 10:06:50 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Mon, 12 Jan 2009 10:07:12 -0700 (MST)
Message-Id: <20090112.100712.107765266.imp@bsdimp.com>
To: pavel@suse.cz
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20090112161115.GA1474@ucw.cz>
References: <alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<20090112161115.GA1474@ucw.cz>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
X-Mailman-Approved-At: Tue, 13 Jan 2009 15:37:26 +0000
Cc: david@lang.hm, goodgerster@gmail.com, kyle@moffetthome.net,
	slashdot@jameshallam.info, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, hancockr@shaw.ca,
	ntpwg@lists.ntp.isc.org, pretzalz@techhouse.org,
	burdell@iruntheinter.net, linasvepstas@gmail.com,
	nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
 new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message: <20090112161115.GA1474@ucw.cz>
            Pavel Machek <pavel@suse.cz> writes:
: On Mon 2009-01-05 11:42:35, Linas Vepstas wrote:
: > 2009/1/5  <david@lang.hm>:
: > > On Mon, 5 Jan 2009, Linas Vepstas wrote:
: > >
: > >>> Arguably the kernel's responsibility should be to keep track of the
: > >>> most fundamental representation of time possible for a machine (that's
: > >>> probably TAI) and it is a userspace responsibility to map from that
: > >>> value to other time standards including UTC,
: > >>
: > >> Yes, this really does seem like the right solution.
: > >>
: > >>> using control files
: > >>> which are updated as leap seconds are declared.
: > >>
: > >> Lets be clear on what "control files" means.  This does
: > >> *NOT* mean some config file shipped by some distro
: > >> for some package. That would be a horrid solution.
: > >> People don't install updates, patches, etc.  Distros
: > >> ship them late, or never, if the distro is old enough.
: > >>
: > >> A more appropriate solution would be to have
: > >> either the kernel or ntpd track the leap seconds
: > >> automatically.  First, the ntp protocol already provides
: > >> the needed notification of a leap second to anyone
: > >> who cares about it (i.e. there is no point in getting a
: > >> Linux distro involved in this -- a distribution mechanism
: > >> already exists, and works *better* than having a distro
: > >> do it).
: > >
: > > I disagree with this. NTP will only know about leap seconds if it was
: > > running and connected to a server that advertised the leap seconds during
: > > that month.
: > >
: > > for example, if you installed a new server today, how would it ever know
: > > that there was a leap second a couple of days ago?
: > 
: > OK, good point.  Unless your distro was less
: > than a few days old (unlikely), you are faced with the
: > same problem.  Sure, eventually, the distro will publish
: > an update (which will add to the existing list of 36 leap
: > seconds -- which is needed in any case, since no one
: > has a server that's been up since 1958),  but this is
: > unlikely to happen during this install window.
: > 
: > The long term solution would be write an RFC to extend
: > NTP to also provide TAI information -- e.g. to add a
: > message that indicates the current leap-second offset
: > between UTC and TAI.
: 
: Offset is not enough; you'd have to provide list of all previous leap
: seconds with 'when it happened' timestamps.

Well, today you can ftp the leapseconds.txt file from NIST.  Of
course, that assumes your machine is on the network, and not a dumb
slave of a smart head-end that's off the net...

Warner
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg


From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Jan 13 07:39:10 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47C1628C18A
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Tue, 13 Jan 2009 07:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sV4YqPMK5noL
	for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>;
	Tue, 13 Jan 2009 07:39:09 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126])
	by core3.amsl.com (Postfix) with ESMTP id 8598128C184
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 13 Jan 2009 07:39:09 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 5543F39F65
	for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 13 Jan 2009 15:38:55 +0000 (UTC)
	(envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1])
	by mail1.ntp.org (Postfix) with ESMTP id 01B2739F37
	for <ntpwg@lists.ntp.isc.org>; Mon, 12 Jan 2009 22:26:20 +0000 (UTC)
	(envelope-from Valdis.Kletnieks@vt.edu)
Received: from mail1.ntp.org ([127.0.0.1])
	by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 30697-05 for <ntpwg@lists.ntp.isc.org>;
	Mon, 12 Jan 2009 22:25:59 +0000 (UTC)
X-Greylist: delayed 2349 seconds by postgrey-1.21 at ntp1.isc.org;
	Mon, 12 Jan 2009 22:25:55 UTC
Received: from turing-police.cc.vt.edu (turing-police.cc.vt.edu
	[128.173.14.107]) by mail1.ntp.org (Postfix) with ESMTP
	for <ntpwg@lists.ntp.isc.org>; Mon, 12 Jan 2009 22:25:16 +0000 (UTC)
	(envelope-from Valdis.Kletnieks@vt.edu)
Received: from turing-police.cc.vt.edu (turing-police.cc.vt.edu [127.0.0.1])
	by turing-police.cc.vt.edu (8.14.3/8.14.3) with ESMTP id n0CLjeHR024813;
	Mon, 12 Jan 2009 16:45:40 -0500
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: Your message of "Mon, 12 Jan 2009 10:07:12 MST."
	<20090112.100712.107765266.imp@bsdimp.com>
From: Valdis.Kletnieks@vt.edu
References: <alpine.DEB.1.10.0901050949560.27641@asgard.lang.hm>
	<3ae3aa420901050942y56f0ecdei39c091a73e49c1fd@mail.gmail.com>
	<20090112161115.GA1474@ucw.cz>
	<20090112.100712.107765266.imp@bsdimp.com>
Mime-Version: 1.0
Date: Mon, 12 Jan 2009 16:45:40 -0500
Message-ID: <24811.1231796740@turing-police.cc.vt.edu>
X-Mailman-Approved-At: Tue, 13 Jan 2009 15:38:00 +0000
Cc: david@lang.hm, goodgerster@gmail.com, kyle@moffetthome.net,
	slashdot@jameshallam.info, davidn@davidnewall.com,
	linux-kernel@vger.kernel.org, hancockr@shaw.ca,
	ntpwg@lists.ntp.isc.org, pavel@suse.cz, pretzalz@techhouse.org,
	burdell@iruntheinter.net, linasvepstas@gmail.com,
	nick@nick-andrew.net, jeff@kosowsky.org
Subject: Re: [ntpwg] Bug: Status/Summary of slashdot leap-second crash on
	new years 2008-2009
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>,
	<mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1124873855=="
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

--===============1124873855==
Content-Type: multipart/signed; boundary="==_Exmh_1231796740_3124P";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit

--==_Exmh_1231796740_3124P
Content-Type: text/plain; charset=us-ascii

On Mon, 12 Jan 2009 10:07:12 MST, "M. Warner Losh" said:

> Well, today you can ftp the leapseconds.txt file from NIST.  Of
> course, that assumes your machine is on the network, and not a dumb
> slave of a smart head-end that's off the net...

If you're a dumb slave off a smart head-end, the sysadmin has already solved
the problem of getting files from the outside to the dumb slave, just for their
own sanity in pushing patches and *other* config file updates.

And if you're *not* getting updates pushed to you for all the *other* stuff,
the leapseconds is probably the least of your worries.


--==_Exmh_1231796740_3124P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQFJa7oEcC3lWbTT17ARAnavAKDCd7uCQchvBinmzsQRHJLfxXq0NgCfX2lk
MbtgaagwhkzhkkTvGurhcTY=
=pM6I
-----END PGP SIGNATURE-----

--==_Exmh_1231796740_3124P--

--===============1124873855==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg
--===============1124873855==--



From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Feb  9 06:32:42 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC6323A6BB0 for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Mon,  9 Feb 2009 06:32:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLXs7MlifEte for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Mon,  9 Feb 2009 06:32:37 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126]) by core3.amsl.com (Postfix) with ESMTP id 54B203A6C88 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  9 Feb 2009 06:32:27 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id A227239FB1 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  9 Feb 2009 14:32:32 +0000 (UTC) (envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id 686B139F86 for <ntpwg@lists.ntp.isc.org>; Mon,  9 Feb 2009 14:31:53 +0000 (UTC) (envelope-from wwwrun@core3.amsl.com)
Received: from mail1.ntp.org ([127.0.0.1]) by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49487-10 for <ntpwg@lists.ntp.isc.org>; Mon,  9 Feb 2009 14:31:38 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138]) by mail1.ntp.org (Postfix) with ESMTP for <ntpwg@lists.ntp.isc.org>; Mon,  9 Feb 2009 14:31:38 +0000 (UTC) (envelope-from wwwrun@core3.amsl.com)
Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:1112:1::20]) by mail2.ntp.org (Postfix) with ESMTP id C37B3398E1 for <ntpwg@lists.ntp.isc.org>; Mon,  9 Feb 2009 14:31:37 +0000 (UTC) (envelope-from wwwrun@core3.amsl.com)
Received: by core3.amsl.com (Postfix, from userid 30) id 44C033A6C1C; Mon,  9 Feb 2009 06:30:49 -0800 (PST)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090209143050.44C033A6C1C@core3.amsl.com>
Date: Mon,  9 Feb 2009 06:30:50 -0800 (PST)
Cc: ntpwg@lists.ntp.isc.org
Subject: [ntpwg] Last Call: draft-ietf-ntp-ntpv4-mib (Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)) to Proposed Standard
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

The IESG has received a request from the Network Time Protocol WG (ntp) 
to consider the following document:

- 'Definitions of Managed Objects for Network Time Protocol Version 4 
   (NTPv4) '
   <draft-ietf-ntp-ntpv4-mib-05.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-02-23. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-mib-05.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14862&rfc_flag=0

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Feb  9 06:47:51 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 198D83A6A90 for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Mon,  9 Feb 2009 06:47:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJHQe7FJqKCq for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Mon,  9 Feb 2009 06:47:50 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126]) by core3.amsl.com (Postfix) with ESMTP id 4636E28C0F4 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  9 Feb 2009 06:47:08 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id C6A0539F91 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  9 Feb 2009 14:47:13 +0000 (UTC) (envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id 360CB39F8B for <ntpwg@lists.ntp.isc.org>; Mon,  9 Feb 2009 14:46:50 +0000 (UTC) (envelope-from wwwrun@core3.amsl.com)
Received: from mail1.ntp.org ([127.0.0.1]) by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71626-01 for <ntpwg@lists.ntp.isc.org>; Mon,  9 Feb 2009 14:46:42 +0000 (UTC)
X-Greylist: delayed 910 seconds by postgrey-1.21 at ntp1.isc.org; Mon, 09 Feb 2009 14:46:42 UTC
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by mail1.ntp.org (Postfix) with ESMTP for <ntpwg@lists.ntp.isc.org>; Mon,  9 Feb 2009 14:46:42 +0000 (UTC) (envelope-from wwwrun@core3.amsl.com)
Received: by core3.amsl.com (Postfix, from userid 30) id 3005A3A6AED; Mon,  9 Feb 2009 06:46:35 -0800 (PST)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090209144636.3005A3A6AED@core3.amsl.com>
Date: Mon,  9 Feb 2009 06:46:36 -0800 (PST)
Cc: ntpwg@lists.ntp.isc.org
Subject: [ntpwg] Last Call: draft-ietf-ntp-ntpv4-proto (Network Time Protocol Version 4 Protocol And Algorithms Specification) to Proposed Standard
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

The IESG has received a request from the Network Time Protocol WG (ntp) 
to consider the following document:

- 'Network Time Protocol Version 4 Protocol And Algorithms Specification '
   <draft-ietf-ntp-ntpv4-proto-11.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-02-23. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-proto-11.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13350&rfc_flag=0

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Feb  9 08:59:32 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 881113A6983 for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Mon,  9 Feb 2009 08:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.14
X-Spam-Level: 
X-Spam-Status: No, score=-3.14 tagged_above=-999 required=5 tests=[AWL=3.459, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51huM+vu2cs9 for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Mon,  9 Feb 2009 08:59:31 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126]) by core3.amsl.com (Postfix) with ESMTP id 0D5D73A6944 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  9 Feb 2009 08:59:27 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id 4C8E339F95 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  9 Feb 2009 16:59:29 +0000 (UTC) (envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id C3F8A39F7E for <ntpwg@lists.ntp.isc.org>; Sun,  8 Feb 2009 20:34:16 +0000 (UTC) (envelope-from bertietf@bwijnen.net)
Received: from mail1.ntp.org ([127.0.0.1]) by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 40820-03 for <ntpwg@lists.ntp.isc.org>; Sun,  8 Feb 2009 20:34:07 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138]) by mail1.ntp.org (Postfix) with ESMTP for <ntpwg@lists.ntp.isc.org>; Sun,  8 Feb 2009 20:34:07 +0000 (UTC) (envelope-from bertietf@bwijnen.net)
Received: from relay.versatel.net (beverwijk.tele2.vuurwerk.nl [62.250.3.53]) by mail2.ntp.org (Postfix) with ESMTP id 10EA339916 for <ntpwg@lists.ntp.isc.org>; Sun,  8 Feb 2009 20:32:48 +0000 (UTC) (envelope-from bertietf@bwijnen.net)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1LWGJy-0007jQ-O0; Sun, 08 Feb 2009 21:32:06 +0100
Message-ID: <3EF7C2B482804D15A054261F369CBFCB@BertLaptop>
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
To: <ntpwg@lists.ntp.isc.org>
Date: Sun, 8 Feb 2009 21:31:40 +0100
Organization: Consultant
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
X-Mailman-Approved-At: Mon, 09 Feb 2009 16:58:55 +0000
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, ops-dir@ietf.org
Subject: [ntpwg] My review of: draft-ietf-ntp-ntpv4-mib-05.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Note: I am not subscribed to the ntpwg mailing list and do not plan to
subscribe either. So if you want me to see any responses, please
copy me explicitly

I did a review for:
    http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-mib-05.txt

Here are my findings:

SMICng results:

  C:\bw\smicng\work>smicng ntpv4.inc
  E: f(ntpv4.mi2), (272,14) Default value for "ntpEntStatusCurrentModeVal"
      must be a name and not a number

   *** 1 error and 0 warnings in parsing

This means changing
    DEFVAL { 99 }
into
    DEFVAL { unknown }
will fix it.

But I also find:

- writable objects for which I see no text in the DESCRIPTION clauses
  about expected persistency behaviour

- Counter32 objects with no test in the DESCRIPTION clauses about
  possible discontinuities and which timer object would indicate such.
  Specifically, the fact that (I think) the ntpd keeps track of the 
Counters,
  it seems that there may be discontinuities at other times than when
  the snmpd restarts (e.g. at other times than reset of sysUpTime)

- I see a whole list of REVISION clauses. Normally we only have a
  single revision clause at RFC publication time. Not a list of revisions
  that took place during I-D revisions.

- I am missing the Copyright statement in the DESCRIPTION clause
  of the MODULE_IDENTITY
- I am missing that this revision of the document is published as RFC xxxx
  (xxxx to be filled in by RFC-editor)

- I see a lot of objects with a SYNTAX of DisplayString.
  I would like to point out "note 2" on web page
       http://www.ops.ietf.org/mib-common-tcs.html
   Note 2.  DisplayString does not support internationalized text.
            It MUST NOT be used for objects that are required to
            hold internationalized text (which is always the case
            if the object is intended for use by humans [RFC2277]).
            Designers SHOULD consider using SnmpAdminString,
            Utf8String, or LongUtf8String for such objects.


- Instead of
     ntpEntNotifPrefix  OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 6 }
     ...
     ntpEntNotifications OBJECT IDENTIFIER ::= { ntpEntNotifPrefix 0 }

  I propose/suggest to do
     ntpEntNotifications OBJECT IDENTIFIER ::= { ntpSnmpMIB 0 }

  This makes it more inline with what we often do in MIB module.
  Also makes the OIDs of notifications shorter

- I strongly recommend to use the MIB structure as per RFC4181,
  which suggests that you would replace
       ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 6 }
  with
       ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 2 }

- I see OBJECT-GROUP definitions like
   ntpEntObjectsGroup1 OBJECT-GROUP
      OBJECTS {
              ntpEntSoftwareName,
              ntpEntSoftwareVersion,
              ntpEntSoftwareVersionVal,
              ntpEntSoftwareVendor,
              ntpEntSystemType,
              ntpEntStatusEntityUptime,
              ntpEntStatusDateTime,
              ntpAssocName,
              ntpAssocRefId,

              ntpAssocAddressType,
              ntpAssocAddress
     }
     STATUS      current
     DESCRIPTION
         "A collection of objects for the NTP MIB that all NTP
          or SNTP entities should implement."
     ::= { ntpEntGroups 1 }

  Text about "should implement" or "optional" or such is NOT supposed to be
  in an OBJECT-GROUP DESCRIPTION clause. The OBJECT-GROUP is
  only meant to group objects logically together.
  If such a group is mandatory or optional is something that is expressed
  via MANDATORY-GROUPS or via the GROUP clauses in the
  MODULE-COMPLIANCE.

 As another example, you have

     ntpEntObjectsGroup2 OBJECT-GROUP
     ...
     DESCRIPTION
        "A collection of objects for the NTP MIB that are optional
         for NTP or SNTP entities to implement."
     ::= { ntpEntGroups 2 }

  So here you say that the group is optional while you have listed this 
group
  as a MANDATORY-GROUP here:

    ntpEntNTPCompliance MODULE-COMPLIANCE
       STATUS      current
       DESCRIPTION
          "The compliance statement for SNMP entities which use NTP and
           implement the NTP MIB"
      MODULE  -- this module
          MANDATORY-GROUPS {
                           ntpEntObjectsGroup1,
                           ntpEntObjectsGroup2,
                           ntpEntNotifPrefixGroup
         }
         ::= { ntpEntCompliances 1 }

  So that is a conflict in your MIB-Module.

- I see a lot of MIB-level comment lines, aka:

  ntpEntSoftwareVersion OBJECT-TYPE
    SYNTAX      DisplayString
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The software version of the installed NTP implementation."
    -- full version string, e.g. "ntpd-4.2.0b@1.1433 ..."
    ::= { ntpEntInfo  2 }

   I think it is much better to include that informatrion in the DESCRIPTION
   clauses. Otherwise it will often be lost when the MIB module is extracted
   or used as input for generating help text etc.

- I see references/citations aka:

NtpDateTime ::= TEXTUAL-CONVENTION
    DISPLAY-HINT "4d:4d:4d.4d"
    STATUS      current
    DESCRIPTION
        "NTP date/time on the device, in 128-bit
         NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06,
         section 6:
          It includes a 64-bit signed seconds field
          spanning 584 billion years and a 64-bit fraction
          field resolving .05 attosecond (i.e. 0.5e-18).
          For convenience in mapping between formats, the
          seconds field is divided into a 32-bit era field
          and a 32-bit timestamp field.

         If time is not syncronized this field shall be a
         zero-length string.

         This TC is not to be used for objects that are used
         to set the time of the node querying this object.

         NTP should be used for this--or at least SNTP."
    SYNTAX      OCTET STRING (SIZE (0 | 16))

  I suggest that the pointer to Ref: draft-ietf-ntp-ntpv4-proto-06
  is changed to Ref: RFC yyyy (and ask RFC-editor to fill in
  that yyyy value. I see that Ref: draft-ietf-ntp-ntpv4-proto-11 is
  also in Last Call, so that would be fine.
  In genreal though, it is probably better to use the REFERENCE
  clause. So it would be something like

    REFERENCE   "Network Time Protocol Version 4 Protocol
                                 And Algorithms Specification, sect 6, RFC 
yyyy"

- It seems to me that for something like this:
   ntpEntStatusEntityUptime OBJECT-TYPE
      SYNTAX      Unsigned32
      MAX-ACCESS  read-only
      STATUS      current
      DESCRIPTION
          "The uptime of the NTP entity in seconds."
      -- time since ntpd was (re-)started (not sysUptime!)
      DEFVAL { 0 }
      ::= { ntpEntStatus 9 }

  I would add a  UNITS clause.
  I would also move the comment line inside the DESCRIPTION clause.
  I am not sure if a DEFVAL of 0 (zero) makes sense.
  Specifically... what would the value be if the snmp agent has started
  later that ntpd? What if the snmp agent restarts and the ntpd does not?
  In fact, I think that a DEFVAL clause makes no sense for this object.

  I in fact wonder if most of the DEFVAL values for the read-only objects
  make sense.

- For
  ntpEntStatPktModeTable OBJECT-TYPE
    SYNTAX           SEQUENCE OF NtpEntStatPktModeEntry
    MAX-ACCESS       not-accessible
    STATUS           current
    DESCRIPTION
        "The number of packets sent and received by packet mode."
    ::= { ntpEntStatus 18 }

  ntpEntStatPktModeEntry OBJECT-TYPE
    SYNTAX      NtpEntStatPktModeEntry
    MAX-ACCESS  not-accessible

    STATUS      current
    DESCRIPTION
        "The number of packets sent and received by packet mode."
    INDEX       { ntpEntStatPktMode }
    ::= { ntpEntStatPktModeTable 1 }

  I am surprised by the SAME DESCRIPTION clause for each of these!!??

- When I see:
ntpAssocAddressType OBJECT-TYPE
    SYNTAX      InetAddressType
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The type of address of the association."
    -- contains the type of address for uni/multi/broadcast associations
    ::= { ntpAssociationEntry 4 }

ntpAssocAddress OBJECT-TYPE
    SYNTAX      InetAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The IP address (IPv4 or IPv6) of the association."
    -- contains IP address of uni/multi/broadcast associations
    ::= { ntpAssociationEntry 5 }

  Then I like to point out that RFC4001 states that the use of InetAddress
  SYNTAX, MUST have a DESCRIPTION clause that explain./states
  which object of SYNTAX InetAddressType controls the format of
  the InetAddress object. It is most probably ntpAssocAddressType
  but it would be good to state so.

  Besides, if you are sure that this ALWAYS only applies to IPv4 and IPv6,
  then I would do it as follows:

    ntpAssocAddressType OBJECT-TYPE
       SYNTAX      InetAddressType { ipv4, ipv6 }

   ntpAssocAddress OBJECT-TYPE
       SYNTAX      InetAddress SIZE(4|16)

 You must check if you also want to use Zoned addressed, because then
  that must be added too.

 If, at the other hand, other values than ipv4/ipv6 are possible (maybe
 in the future?) then it might be better to put the "minimum support for
 ipv4/ipv6 requirement in the MODULE-COMPLIANCE via an OBJECT
 and SYNTAX clause.

- I see some 8 notifications. Is there a risk that too many get generated
  at any point in time, such that it would flood the network and/or
  overload a NMS ??
  It would be good to add some text about the expected max notification
  rates and/or add a throthle or an enable/disable switch.

- It seems that RFC4001 is missing as a normative reference.

- I would think that the new draft-ietf-ntp-ntpv4-proto-11 (version 4 of 
NTP)
  should also be a normative reference

- The security section is not according to the guidelines provided at
       http://www.ops.ietf.org/mib-security.html

- I have not checked the new NTP version 4 spec to see if the knobs/sensors
  in that protocol have properly been modeled in this MIB module.
  That is a separate task that may actually need much more time than the
  review I have done for now.

Bert Wijnen 

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Feb 18 23:21:30 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8397C3A6783 for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed, 18 Feb 2009 23:21:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fe5QP-1MwMen for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed, 18 Feb 2009 23:21:28 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126]) by core3.amsl.com (Postfix) with ESMTP id D3A363A6A35 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 18 Feb 2009 23:21:25 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id 8331439F97 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 19 Feb 2009 07:21:37 +0000 (UTC) (envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id 0308F39F93 for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 07:20:42 +0000 (UTC) (envelope-from heiko.gerstung@meinberg.de)
Received: from mail1.ntp.org ([127.0.0.1]) by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75997-04 for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 07:20:13 +0000 (UTC)
Received: from server1.meinberg.de (server1.meinberg.de [85.10.202.66]) by mail1.ntp.org (Postfix) with ESMTP for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 07:20:12 +0000 (UTC) (envelope-from heiko.gerstung@meinberg.de)
Received: from localhost (localhost [127.0.0.1]) by server1.meinberg.de (Postfix) with ESMTP id 1A77F2EE259; Thu, 19 Feb 2009 08:20:11 +0100 (CET)
Received: from server1.meinberg.de ([127.0.0.1]) by localhost (server1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07071-08; Thu, 19 Feb 2009 08:20:08 +0100 (CET)
Received: from gateway.py.meinberg.de (unknown [217.5.178.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by server1.meinberg.de (Postfix) with ESMTP id BAA022EE256; Thu, 19 Feb 2009 08:20:07 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by gateway.py.meinberg.de (Postfix) with ESMTP id 4F5601DBDE4; Thu, 19 Feb 2009 08:20:07 +0100 (CET)
Received: from gateway.py.meinberg.de ([127.0.0.1]) by localhost (gateway [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09230-08; Thu, 19 Feb 2009 08:19:57 +0100 (CET)
Received: from [172.16.3.144] (pc-heiko.py.meinberg.de [172.16.3.144]) by gateway.py.meinberg.de (Postfix) with ESMTP id 69E491DBE18; Thu, 19 Feb 2009 08:19:57 +0100 (CET)
Message-ID: <499D081D.7020109@meinberg.de>
Date: Thu, 19 Feb 2009 08:19:57 +0100
From: Heiko Gerstung <heiko.gerstung@meinberg.de>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <3EF7C2B482804D15A054261F369CBFCB@BertLaptop>
In-Reply-To: <3EF7C2B482804D15A054261F369CBFCB@BertLaptop>
X-Virus-Scanned: amavisd-new at py.meinberg.de
X-Virus-Scanned: amavisd-new at meinberg.de
Cc: ntpwg@lists.ntp.isc.org
Subject: Re: [ntpwg] My review of: draft-ietf-ntp-ntpv4-mib-05.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Bert,

thank you very much for your detailed and useful review of our MIB 
module. I will try to implement as many points as possible but I am 
unsure what that does to the standardization process (it is my first RFC 
....). It took us all a long time to get into last call and I am a 
little bit scared that the modifications will restart the whole 
procedure again. I asked my wg chair for advise what to do.

See my additional comments below (inline):

Bert Wijnen (IETF) schrieb:
> Note: I am not subscribed to the ntpwg mailing list and do not plan to
> subscribe either. So if you want me to see any responses, please
> copy me explicitly
>
> I did a review for:
>    http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-mib-05.txt
>
> Here are my findings:
>
> SMICng results:
>
>  C:\bw\smicng\work>smicng ntpv4.inc
>  E: f(ntpv4.mi2), (272,14) Default value for "ntpEntStatusCurrentModeVal"
>      must be a name and not a number
>
>   *** 1 error and 0 warnings in parsing
>
> This means changing
>    DEFVAL { 99 }
> into
>    DEFVAL { unknown }
> will fix it.
Strange, I used smilint at level 6 and did not get any errors. This is 
an easy fix, though.
> But I also find:
>
> - writable objects for which I see no text in the DESCRIPTION clauses
>  about expected persistency behaviour
That means you want to know whether an object stores the changes on that 
object permanently or not? I am not sure if this is not 
implementation-specific.
> - Counter32 objects with no test in the DESCRIPTION clauses about
>  possible discontinuities and which timer object would indicate such.
>  Specifically, the fact that (I think) the ntpd keeps track of the 
> Counters,
>  it seems that there may be discontinuities at other times than when
>  the snmpd restarts (e.g. at other times than reset of sysUpTime)
Not sure what you mean, can you please provide me with an example?
> - I see a whole list of REVISION clauses. Normally we only have a
>  single revision clause at RFC publication time. Not a list of revisions
>  that took place during I-D revisions.
OK.
> - I am missing the Copyright statement in the DESCRIPTION clause
>  of the MODULE_IDENTITY
I guess this has been overseen but can be added quite easily. Where can 
I find the required copyright statement in its correct form?
> - I am missing that this revision of the document is published as RFC 
> xxxx
>  (xxxx to be filled in by RFC-editor)
OK.
> - I see a lot of objects with a SYNTAX of DisplayString.
>  I would like to point out "note 2" on web page
>       http://www.ops.ietf.org/mib-common-tcs.html
>   Note 2.  DisplayString does not support internationalized text.
>            It MUST NOT be used for objects that are required to
>            hold internationalized text (which is always the case
>            if the object is intended for use by humans [RFC2277]).
>            Designers SHOULD consider using SnmpAdminString,
>            Utf8String, or LongUtf8String for such objects.
The DisplayString objects are mainly used for values which require to be 
floating point and we agreed in the working group discussions that it 
would make sense to use a string instead that can be converted into an 
fp value by a machine.
> - Instead of
>     ntpEntNotifPrefix  OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 6 }
>     ...
>     ntpEntNotifications OBJECT IDENTIFIER ::= { ntpEntNotifPrefix 0 }
>
>  I propose/suggest to do
>     ntpEntNotifications OBJECT IDENTIFIER ::= { ntpSnmpMIB 0 }
>
>  This makes it more inline with what we often do in MIB module.
>  Also makes the OIDs of notifications shorter
OK, agreed.
> - I strongly recommend to use the MIB structure as per RFC4181,
>  which suggests that you would replace
>       ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 6 }
>  with
>       ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 2 }
>
OK.
> - I see OBJECT-GROUP definitions like
>   ntpEntObjectsGroup1 OBJECT-GROUP
>      OBJECTS {
>              ntpEntSoftwareName,
>              ntpEntSoftwareVersion,
>              ntpEntSoftwareVersionVal,
>              ntpEntSoftwareVendor,
>              ntpEntSystemType,
>              ntpEntStatusEntityUptime,
>              ntpEntStatusDateTime,
>              ntpAssocName,
>              ntpAssocRefId,
>
>              ntpAssocAddressType,
>              ntpAssocAddress
>     }
>     STATUS      current
>     DESCRIPTION
>         "A collection of objects for the NTP MIB that all NTP
>          or SNTP entities should implement."
>     ::= { ntpEntGroups 1 }
>
>  Text about "should implement" or "optional" or such is NOT supposed 
> to be
>  in an OBJECT-GROUP DESCRIPTION clause. The OBJECT-GROUP is
>  only meant to group objects logically together.
>  If such a group is mandatory or optional is something that is expressed
>  via MANDATORY-GROUPS or via the GROUP clauses in the
>  MODULE-COMPLIANCE.
OK, I will remove the text from the description and change the group 
clauses accordingly.
> As another example, you have
>
>     ntpEntObjectsGroup2 OBJECT-GROUP
>     ...
>     DESCRIPTION
>        "A collection of objects for the NTP MIB that are optional
>         for NTP or SNTP entities to implement."
>     ::= { ntpEntGroups 2 }
>
>  So here you say that the group is optional while you have listed this 
> group
>  as a MANDATORY-GROUP here:
>
>    ntpEntNTPCompliance MODULE-COMPLIANCE
>       STATUS      current
>       DESCRIPTION
>          "The compliance statement for SNMP entities which use NTP and
>           implement the NTP MIB"
>      MODULE  -- this module
>          MANDATORY-GROUPS {
>                           ntpEntObjectsGroup1,
>                           ntpEntObjectsGroup2,
>                           ntpEntNotifPrefixGroup
>         }
>         ::= { ntpEntCompliances 1 }
>
>  So that is a conflict in your MIB-Module.
OK.
> - I see a lot of MIB-level comment lines, aka:
>
>  ntpEntSoftwareVersion OBJECT-TYPE
>    SYNTAX      DisplayString
>    MAX-ACCESS  read-only
>    STATUS      current
>    DESCRIPTION
>        "The software version of the installed NTP implementation."
>    -- full version string, e.g. "ntpd-4.2.0b@1.1433 ..."
>    ::= { ntpEntInfo  2 }
>
>   I think it is much better to include that informatrion in the 
> DESCRIPTION
>   clauses. Otherwise it will often be lost when the MIB module is 
> extracted
>   or used as input for generating help text etc.
Good point, noted.
> - I see references/citations aka:
>
> NtpDateTime ::= TEXTUAL-CONVENTION
>    DISPLAY-HINT "4d:4d:4d.4d"
>    STATUS      current
>    DESCRIPTION
>        "NTP date/time on the device, in 128-bit
>         NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06,
>         section 6:
>          It includes a 64-bit signed seconds field
>          spanning 584 billion years and a 64-bit fraction
>          field resolving .05 attosecond (i.e. 0.5e-18).
>          For convenience in mapping between formats, the
>          seconds field is divided into a 32-bit era field
>          and a 32-bit timestamp field.
>
>         If time is not syncronized this field shall be a
>         zero-length string.
>
>         This TC is not to be used for objects that are used
>         to set the time of the node querying this object.
>
>         NTP should be used for this--or at least SNTP."
>    SYNTAX      OCTET STRING (SIZE (0 | 16))
>
>  I suggest that the pointer to Ref: draft-ietf-ntp-ntpv4-proto-06
>  is changed to Ref: RFC yyyy (and ask RFC-editor to fill in
>  that yyyy value. I see that Ref: draft-ietf-ntp-ntpv4-proto-11 is
>  also in Last Call, so that would be fine.
>  In genreal though, it is probably better to use the REFERENCE
>  clause. So it would be something like
>
>    REFERENCE   "Network Time Protocol Version 4 Protocol
>                                 And Algorithms Specification, sect 6, 
> RFC yyyy"
>
OK, makes perfect sense.
> - It seems to me that for something like this:
>   ntpEntStatusEntityUptime OBJECT-TYPE
>      SYNTAX      Unsigned32
>      MAX-ACCESS  read-only
>      STATUS      current
>      DESCRIPTION
>          "The uptime of the NTP entity in seconds."
>      -- time since ntpd was (re-)started (not sysUptime!)
>      DEFVAL { 0 }
>      ::= { ntpEntStatus 9 }
>
>  I would add a  UNITS clause.
>  I would also move the comment line inside the DESCRIPTION clause.
>  I am not sure if a DEFVAL of 0 (zero) makes sense.
>  Specifically... what would the value be if the snmp agent has started
>  later that ntpd? What if the snmp agent restarts and the ntpd does not?
>  In fact, I think that a DEFVAL clause makes no sense for this object.
Agreed, I will remove the DEFAL line. Can you provide me with an example 
on how to use the UNITS clause?

>  I in fact wonder if most of the DEFVAL values for the read-only objects
>  make sense.
>
> - For
>  ntpEntStatPktModeTable OBJECT-TYPE
>    SYNTAX           SEQUENCE OF NtpEntStatPktModeEntry
>    MAX-ACCESS       not-accessible
>    STATUS           current
>    DESCRIPTION
>        "The number of packets sent and received by packet mode."
>    ::= { ntpEntStatus 18 }
>
>  ntpEntStatPktModeEntry OBJECT-TYPE
>    SYNTAX      NtpEntStatPktModeEntry
>    MAX-ACCESS  not-accessible
>
>    STATUS      current
>    DESCRIPTION
>        "The number of packets sent and received by packet mode."
>    INDEX       { ntpEntStatPktMode }
>    ::= { ntpEntStatPktModeTable 1 }
>
>  I am surprised by the SAME DESCRIPTION clause for each of these!!??
I will change that.
> - When I see:
> ntpAssocAddressType OBJECT-TYPE
>    SYNTAX      InetAddressType
>    MAX-ACCESS  read-only
>    STATUS      current
>    DESCRIPTION
>        "The type of address of the association."
>    -- contains the type of address for uni/multi/broadcast associations
>    ::= { ntpAssociationEntry 4 }
>
> ntpAssocAddress OBJECT-TYPE
>    SYNTAX      InetAddress
>    MAX-ACCESS  read-only
>    STATUS      current
>    DESCRIPTION
>        "The IP address (IPv4 or IPv6) of the association."
>    -- contains IP address of uni/multi/broadcast associations
>    ::= { ntpAssociationEntry 5 }
>
>  Then I like to point out that RFC4001 states that the use of InetAddress
>  SYNTAX, MUST have a DESCRIPTION clause that explain./states
>  which object of SYNTAX InetAddressType controls the format of
>  the InetAddress object. It is most probably ntpAssocAddressType
>  but it would be good to state so.
>
>  Besides, if you are sure that this ALWAYS only applies to IPv4 and IPv6,
>  then I would do it as follows:
>
>    ntpAssocAddressType OBJECT-TYPE
>       SYNTAX      InetAddressType { ipv4, ipv6 }
>
>   ntpAssocAddress OBJECT-TYPE
>       SYNTAX      InetAddress SIZE(4|16)
>
Thanks, I will do it this way because we currently only have NTP over 
IPv4 and IPv6 - to my knowledge.
> You must check if you also want to use Zoned addressed, because then
>  that must be added too.
Any thoughts on that by anybody?
> If, at the other hand, other values than ipv4/ipv6 are possible (maybe
> in the future?) then it might be better to put the "minimum support for
> ipv4/ipv6 requirement in the MODULE-COMPLIANCE via an OBJECT
> and SYNTAX clause.
Again, since this is my first MIB I would appreciate an example.
>
> - I see some 8 notifications. Is there a risk that too many get generated
>  at any point in time, such that it would flood the network and/or
>  overload a NMS ??
>  It would be good to add some text about the expected max notification
>  rates and/or add a throthle or an enable/disable switch.
OK, I will look into this.
> - It seems that RFC4001 is missing as a normative reference.
OK.
> - I would think that the new draft-ietf-ntp-ntpv4-proto-11 (version 4 
> of NTP)
>  should also be a normative reference
Shouldn't we use the RFC yyyy approach instead (yyyy being the 
to-be-assigned RFC for the protocol RFC)?
> - The security section is not according to the guidelines provided at
>       http://www.ops.ietf.org/mib-security.html
I unfortunately currently seem to be unable to access this website (and 
www.ietf.org as well), but I think it would be helpful to know which 
points are missing / wrong in your oppinion.
>
> - I have not checked the new NTP version 4 spec to see if the 
> knobs/sensors
>  in that protocol have properly been modeled in this MIB module.
>  That is a separate task that may actually need much more time than the
>  review I have done for now.
Since this has been discussed in the working group I would expect that 
everybody is happy with what is in the MIB right now. But I really 
appreciate your efforts and your very detailed review of this document. 
I only wish we would have somebody sending me such a review earlier in 
the process, before everything went into last call. Anyway, you did a 
great job and I think this was a very useful review. I will go back to 
my drawing desk and start to implement the advised changes.

Best Regards,
  Heiko

> Bert Wijnen

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Thu Feb 19 09:09:30 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 917013A682E for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu, 19 Feb 2009 09:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CXHFtv5wb+xW for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Thu, 19 Feb 2009 09:09:29 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126]) by core3.amsl.com (Postfix) with ESMTP id 1405E3A67F7 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 19 Feb 2009 09:09:29 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id C171C39FB2 for <ntp-archives-ahFae6za@lists.ietf.org>; Thu, 19 Feb 2009 17:09:41 +0000 (UTC) (envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id D3A8339F7D for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 17:08:44 +0000 (UTC) (envelope-from karen.odonoghue@navy.mil)
Received: from mail1.ntp.org ([127.0.0.1]) by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 40905-03 for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 17:08:26 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138]) by mail1.ntp.org (Postfix) with ESMTP for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 17:08:24 +0000 (UTC) (envelope-from karen.odonoghue@navy.mil)
Received: from gate4-norfolk.nmci.navy.mil (gate4-norfolk.nmci.navy.mil [138.162.0.44]) by mail2.ntp.org (Postfix) with ESMTP id 9CAD2399CC for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 17:06:59 +0000 (UTC) (envelope-from karen.odonoghue@navy.mil)
Received: from NAEANRFKEG05.nadsusea.nads.navy.mil ([10.16.0.164]) by gate4-norfolk.nmci.navy.mil with Microsoft SMTPSVC(5.0.2195.6872);  Thu, 19 Feb 2009 12:17:34 -0500
Received: from NAEANRFKEB09.nadsusea.nads.navy.mil ([10.16.20.174]) by NAEANRFKEG05.nadsusea.nads.navy.mil with Microsoft SMTPSVC(5.0.2195.6713); Thu, 19 Feb 2009 12:06:17 -0500
Received: from NAEAMILLEB02.nadsusea.nads.navy.mil ([10.18.183.10]) by NAEANRFKEB09.nadsusea.nads.navy.mil with Microsoft SMTPSVC(5.0.2195.6713); Thu, 19 Feb 2009 12:06:17 -0500
Received: from naeamillez05v.nadsusea.nads.navy.mil ([10.18.183.82]) by NAEAMILLEB02.nadsusea.nads.navy.mil with Microsoft SMTPSVC(5.0.2195.6713); Thu, 19 Feb 2009 11:06:14 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 19 Feb 2009 11:06:14 -0600
Message-ID: <AE47D7F85F757B46BDDB9D9366F991C01CCB98@naeamillez05v.nadsusea.nads.navy.mil>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ntpwg] My review of: draft-ietf-ntp-ntpv4-mib-05.txt
thread-index: AcmSYs//QKewOK9UQc+n7YJpd8j1QAAUY4YF
From: "Odonoghue, Karen F CIV NSWCDD, W23" <karen.odonoghue@navy.mil>
To: <heiko.gerstung@meinberg.de>, <bertietf@bwijnen.net>
X-OriginalArrivalTime: 19 Feb 2009 17:06:14.0421 (UTC) FILETIME=[5F1C0450:01C992B4]
Cc: ntpwg@lists.ntp.isc.org
Subject: Re: [ntpwg] My review of: draft-ietf-ntp-ntpv4-mib-05.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Heiko,

I'm driving and need to answer via blackberry. The short answer is we need to make the changesd. Bert is part of the official review process. I finally go to Chris. Email him at chelliot@pobox.com. I will give you a more coherent answer when I arrive at my destination.

Karen

----- Original Message -----
From: ntpwg-bounces+karen.odonoghue=navy.mil@lists.ntp.org <ntpwg-bounces+karen.odonoghue=navy.mil@lists.ntp.org>
To: Bert Wijnen (IETF) <bertietf@bwijnen.net>
Cc: ntpwg@lists.ntp.isc.org <ntpwg@lists.ntp.isc.org>
Sent: Thu Feb 19 02:19:57 2009
Subject: Re: [ntpwg] My review of: draft-ietf-ntp-ntpv4-mib-05.txt

Bert,

thank you very much for your detailed and useful review of our MIB 
module. I will try to implement as many points as possible but I am 
unsure what that does to the standardization process (it is my first RFC 
....). It took us all a long time to get into last call and I am a 
little bit scared that the modifications will restart the whole 
procedure again. I asked my wg chair for advise what to do.

See my additional comments below (inline):

Bert Wijnen (IETF) schrieb:
> Note: I am not subscribed to the ntpwg mailing list and do not plan to
> subscribe either. So if you want me to see any responses, please
> copy me explicitly
>
> I did a review for:
>    http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-mib-05.txt
>
> Here are my findings:
>
> SMICng results:
>
>  C:\bw\smicng\work>smicng ntpv4.inc
>  E: f(ntpv4.mi2), (272,14) Default value for "ntpEntStatusCurrentModeVal"
>      must be a name and not a number
>
>   *** 1 error and 0 warnings in parsing
>
> This means changing
>    DEFVAL { 99 }
> into
>    DEFVAL { unknown }
> will fix it.
Strange, I used smilint at level 6 and did not get any errors. This is 
an easy fix, though.
> But I also find:
>
> - writable objects for which I see no text in the DESCRIPTION clauses
>  about expected persistency behaviour
That means you want to know whether an object stores the changes on that 
object permanently or not? I am not sure if this is not 
implementation-specific.
> - Counter32 objects with no test in the DESCRIPTION clauses about
>  possible discontinuities and which timer object would indicate such.
>  Specifically, the fact that (I think) the ntpd keeps track of the 
> Counters,
>  it seems that there may be discontinuities at other times than when
>  the snmpd restarts (e.g. at other times than reset of sysUpTime)
Not sure what you mean, can you please provide me with an example?
> - I see a whole list of REVISION clauses. Normally we only have a
>  single revision clause at RFC publication time. Not a list of revisions
>  that took place during I-D revisions.
OK.
> - I am missing the Copyright statement in the DESCRIPTION clause
>  of the MODULE_IDENTITY
I guess this has been overseen but can be added quite easily. Where can 
I find the required copyright statement in its correct form?
> - I am missing that this revision of the document is published as RFC 
> xxxx
>  (xxxx to be filled in by RFC-editor)
OK.
> - I see a lot of objects with a SYNTAX of DisplayString.
>  I would like to point out "note 2" on web page
>       http://www.ops.ietf.org/mib-common-tcs.html
>   Note 2.  DisplayString does not support internationalized text.
>            It MUST NOT be used for objects that are required to
>            hold internationalized text (which is always the case
>            if the object is intended for use by humans [RFC2277]).
>            Designers SHOULD consider using SnmpAdminString,
>            Utf8String, or LongUtf8String for such objects.
The DisplayString objects are mainly used for values which require to be 
floating point and we agreed in the working group discussions that it 
would make sense to use a string instead that can be converted into an 
fp value by a machine.
> - Instead of
>     ntpEntNotifPrefix  OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 6 }
>     ...
>     ntpEntNotifications OBJECT IDENTIFIER ::= { ntpEntNotifPrefix 0 }
>
>  I propose/suggest to do
>     ntpEntNotifications OBJECT IDENTIFIER ::= { ntpSnmpMIB 0 }
>
>  This makes it more inline with what we often do in MIB module.
>  Also makes the OIDs of notifications shorter
OK, agreed.
> - I strongly recommend to use the MIB structure as per RFC4181,
>  which suggests that you would replace
>       ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 6 }
>  with
>       ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 2 }
>
OK.
> - I see OBJECT-GROUP definitions like
>   ntpEntObjectsGroup1 OBJECT-GROUP
>      OBJECTS {
>              ntpEntSoftwareName,
>              ntpEntSoftwareVersion,
>              ntpEntSoftwareVersionVal,
>              ntpEntSoftwareVendor,
>              ntpEntSystemType,
>              ntpEntStatusEntityUptime,
>              ntpEntStatusDateTime,
>              ntpAssocName,
>              ntpAssocRefId,
>
>              ntpAssocAddressType,
>              ntpAssocAddress
>     }
>     STATUS      current
>     DESCRIPTION
>         "A collection of objects for the NTP MIB that all NTP
>          or SNTP entities should implement."
>     ::= { ntpEntGroups 1 }
>
>  Text about "should implement" or "optional" or such is NOT supposed 
> to be
>  in an OBJECT-GROUP DESCRIPTION clause. The OBJECT-GROUP is
>  only meant to group objects logically together.
>  If such a group is mandatory or optional is something that is expressed
>  via MANDATORY-GROUPS or via the GROUP clauses in the
>  MODULE-COMPLIANCE.
OK, I will remove the text from the description and change the group 
clauses accordingly.
> As another example, you have
>
>     ntpEntObjectsGroup2 OBJECT-GROUP
>     ...
>     DESCRIPTION
>        "A collection of objects for the NTP MIB that are optional
>         for NTP or SNTP entities to implement."
>     ::= { ntpEntGroups 2 }
>
>  So here you say that the group is optional while you have listed this 
> group
>  as a MANDATORY-GROUP here:
>
>    ntpEntNTPCompliance MODULE-COMPLIANCE
>       STATUS      current
>       DESCRIPTION
>          "The compliance statement for SNMP entities which use NTP and
>           implement the NTP MIB"
>      MODULE  -- this module
>          MANDATORY-GROUPS {
>                           ntpEntObjectsGroup1,
>                           ntpEntObjectsGroup2,
>                           ntpEntNotifPrefixGroup
>         }
>         ::= { ntpEntCompliances 1 }
>
>  So that is a conflict in your MIB-Module.
OK.
> - I see a lot of MIB-level comment lines, aka:
>
>  ntpEntSoftwareVersion OBJECT-TYPE
>    SYNTAX      DisplayString
>    MAX-ACCESS  read-only
>    STATUS      current
>    DESCRIPTION
>        "The software version of the installed NTP implementation."
>    -- full version string, e.g. "ntpd-4.2.0b@1.1433 ..."
>    ::= { ntpEntInfo  2 }
>
>   I think it is much better to include that informatrion in the 
> DESCRIPTION
>   clauses. Otherwise it will often be lost when the MIB module is 
> extracted
>   or used as input for generating help text etc.
Good point, noted.
> - I see references/citations aka:
>
> NtpDateTime ::= TEXTUAL-CONVENTION
>    DISPLAY-HINT "4d:4d:4d.4d"
>    STATUS      current
>    DESCRIPTION
>        "NTP date/time on the device, in 128-bit
>         NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06,
>         section 6:
>          It includes a 64-bit signed seconds field
>          spanning 584 billion years and a 64-bit fraction
>          field resolving .05 attosecond (i.e. 0.5e-18).
>          For convenience in mapping between formats, the
>          seconds field is divided into a 32-bit era field
>          and a 32-bit timestamp field.
>
>         If time is not syncronized this field shall be a
>         zero-length string.
>
>         This TC is not to be used for objects that are used
>         to set the time of the node querying this object.
>
>         NTP should be used for this--or at least SNTP."
>    SYNTAX      OCTET STRING (SIZE (0 | 16))
>
>  I suggest that the pointer to Ref: draft-ietf-ntp-ntpv4-proto-06
>  is changed to Ref: RFC yyyy (and ask RFC-editor to fill in
>  that yyyy value. I see that Ref: draft-ietf-ntp-ntpv4-proto-11 is
>  also in Last Call, so that would be fine.
>  In genreal though, it is probably better to use the REFERENCE
>  clause. So it would be something like
>
>    REFERENCE   "Network Time Protocol Version 4 Protocol
>                                 And Algorithms Specification, sect 6, 
> RFC yyyy"
>
OK, makes perfect sense.
> - It seems to me that for something like this:
>   ntpEntStatusEntityUptime OBJECT-TYPE
>      SYNTAX      Unsigned32
>      MAX-ACCESS  read-only
>      STATUS      current
>      DESCRIPTION
>          "The uptime of the NTP entity in seconds."
>      -- time since ntpd was (re-)started (not sysUptime!)
>      DEFVAL { 0 }
>      ::= { ntpEntStatus 9 }
>
>  I would add a  UNITS clause.
>  I would also move the comment line inside the DESCRIPTION clause.
>  I am not sure if a DEFVAL of 0 (zero) makes sense.
>  Specifically... what would the value be if the snmp agent has started
>  later that ntpd? What if the snmp agent restarts and the ntpd does not?
>  In fact, I think that a DEFVAL clause makes no sense for this object.
Agreed, I will remove the DEFAL line. Can you provide me with an example 
on how to use the UNITS clause?

>  I in fact wonder if most of the DEFVAL values for the read-only objects
>  make sense.
>
> - For
>  ntpEntStatPktModeTable OBJECT-TYPE
>    SYNTAX           SEQUENCE OF NtpEntStatPktModeEntry
>    MAX-ACCESS       not-accessible
>    STATUS           current
>    DESCRIPTION
>        "The number of packets sent and received by packet mode."
>    ::= { ntpEntStatus 18 }
>
>  ntpEntStatPktModeEntry OBJECT-TYPE
>    SYNTAX      NtpEntStatPktModeEntry
>    MAX-ACCESS  not-accessible
>
>    STATUS      current
>    DESCRIPTION
>        "The number of packets sent and received by packet mode."
>    INDEX       { ntpEntStatPktMode }
>    ::= { ntpEntStatPktModeTable 1 }
>
>  I am surprised by the SAME DESCRIPTION clause for each of these!!??
I will change that.
> - When I see:
> ntpAssocAddressType OBJECT-TYPE
>    SYNTAX      InetAddressType
>    MAX-ACCESS  read-only
>    STATUS      current
>    DESCRIPTION
>        "The type of address of the association."
>    -- contains the type of address for uni/multi/broadcast associations
>    ::= { ntpAssociationEntry 4 }
>
> ntpAssocAddress OBJECT-TYPE
>    SYNTAX      InetAddress
>    MAX-ACCESS  read-only
>    STATUS      current
>    DESCRIPTION
>        "The IP address (IPv4 or IPv6) of the association."
>    -- contains IP address of uni/multi/broadcast associations
>    ::= { ntpAssociationEntry 5 }
>
>  Then I like to point out that RFC4001 states that the use of InetAddress
>  SYNTAX, MUST have a DESCRIPTION clause that explain./states
>  which object of SYNTAX InetAddressType controls the format of
>  the InetAddress object. It is most probably ntpAssocAddressType
>  but it would be good to state so.
>
>  Besides, if you are sure that this ALWAYS only applies to IPv4 and IPv6,
>  then I would do it as follows:
>
>    ntpAssocAddressType OBJECT-TYPE
>       SYNTAX      InetAddressType { ipv4, ipv6 }
>
>   ntpAssocAddress OBJECT-TYPE
>       SYNTAX      InetAddress SIZE(4|16)
>
Thanks, I will do it this way because we currently only have NTP over 
IPv4 and IPv6 - to my knowledge.
> You must check if you also want to use Zoned addressed, because then
>  that must be added too.
Any thoughts on that by anybody?
> If, at the other hand, other values than ipv4/ipv6 are possible (maybe
> in the future?) then it might be better to put the "minimum support for
> ipv4/ipv6 requirement in the MODULE-COMPLIANCE via an OBJECT
> and SYNTAX clause.
Again, since this is my first MIB I would appreciate an example.
>
> - I see some 8 notifications. Is there a risk that too many get generated
>  at any point in time, such that it would flood the network and/or
>  overload a NMS ??
>  It would be good to add some text about the expected max notification
>  rates and/or add a throthle or an enable/disable switch.
OK, I will look into this.
> - It seems that RFC4001 is missing as a normative reference.
OK.
> - I would think that the new draft-ietf-ntp-ntpv4-proto-11 (version 4 
> of NTP)
>  should also be a normative reference
Shouldn't we use the RFC yyyy approach instead (yyyy being the 
to-be-assigned RFC for the protocol RFC)?
> - The security section is not according to the guidelines provided at
>       http://www.ops.ietf.org/mib-security.html
I unfortunately currently seem to be unable to access this website (and 
www.ietf.org as well), but I think it would be helpful to know which 
points are missing / wrong in your oppinion.
>
> - I have not checked the new NTP version 4 spec to see if the 
> knobs/sensors
>  in that protocol have properly been modeled in this MIB module.
>  That is a separate task that may actually need much more time than the
>  review I have done for now.
Since this has been discussed in the working group I would expect that 
everybody is happy with what is in the MIB right now. But I really 
appreciate your efforts and your very detailed review of this document. 
I only wish we would have somebody sending me such a review earlier in 
the process, before everything went into last call. Anyway, you did a 
great job and I think this was a very useful review. I will go back to 
my drawing desk and start to implement the advised changes.

Best Regards,
  Heiko

> Bert Wijnen

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Feb 20 07:48:52 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 21F303A6B0F for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Fri, 20 Feb 2009 07:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.159
X-Spam-Level: 
X-Spam-Status: No, score=-3.159 tagged_above=-999 required=5 tests=[AWL=3.440, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jw7ajZcbf53l for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Fri, 20 Feb 2009 07:48:50 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126]) by core3.amsl.com (Postfix) with ESMTP id 71C733A6BC5 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri, 20 Feb 2009 07:48:50 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id D669839F97 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri, 20 Feb 2009 15:49:03 +0000 (UTC) (envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id F169339FA1 for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 23:07:30 +0000 (UTC) (envelope-from bertietf@bwijnen.net)
Received: from mail1.ntp.org ([127.0.0.1]) by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85157-01 for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 23:07:17 +0000 (UTC)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138]) by mail1.ntp.org (Postfix) with ESMTP for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 23:07:17 +0000 (UTC) (envelope-from bertietf@bwijnen.net)
Received: from relay.versatel.net (beverwijk.tele2.vuurwerk.nl [62.250.3.53]) by mail2.ntp.org (Postfix) with ESMTP id 2927639941 for <ntpwg@lists.ntp.isc.org>; Thu, 19 Feb 2009 23:05:58 +0000 (UTC) (envelope-from bertietf@bwijnen.net)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1LaHxE-0005qQ-TS; Fri, 20 Feb 2009 00:05:17 +0100
Message-ID: <A66203920E184B50B2C91DD7BC9D7D93@BertLaptop>
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
To: "Heiko Gerstung" <heiko.gerstung@meinberg.de>
References: <3EF7C2B482804D15A054261F369CBFCB@BertLaptop> <499D081D.7020109@meinberg.de>
In-Reply-To: <499D081D.7020109@meinberg.de>
Date: Fri, 20 Feb 2009 00:05:01 +0100
Organization: Consultant
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
X-Mailman-Approved-At: Fri, 20 Feb 2009 15:48:20 +0000
Cc: ntpwg@lists.ntp.isc.org, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [ntpwg] My review of: draft-ietf-ntp-ntpv4-mib-05.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

inline
----- Original Message ----- 
From: Heiko Gerstung
To: Bert Wijnen (IETF)
Cc: ntpwg@lists.ntp.isc.org
Sent: Thursday, February 19, 2009 8:19 AM
Subject: Re: My review of: draft-ietf-ntp-ntpv4-mib-05.txt


Bert,

thank you very much for your detailed and useful review of our MIB
module. I will try to implement as many points as possible but I am
unsure what that does to the standardization process (it is my first RFC
....). It took us all a long time to get into last call and I am a
little bit scared that the modifications will restart the whole
procedure again. I asked my wg chair for advise what to do.

See my additional comments below (inline):

Bert Wijnen (IETF) schrieb:
> Note: I am not subscribed to the ntpwg mailing list and do not plan to
> subscribe either. So if you want me to see any responses, please
> copy me explicitly
>
> I did a review for:
>    http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-mib-05.txt
>
> Here are my findings:
>
> SMICng results:
>
>  C:\bw\smicng\work>smicng ntpv4.inc
>  E: f(ntpv4.mi2), (272,14) Default value for "ntpEntStatusCurrentModeVal"
>      must be a name and not a number
>
>   *** 1 error and 0 warnings in parsing
>
> This means changing
>    DEFVAL { 99 }
> into
>    DEFVAL { unknown }
> will fix it.
Strange, I used smilint at level 6 and did not get any errors. This is
an easy fix, though.
> But I also find:
>
> - writable objects for which I see no text in the DESCRIPTION clauses
>  about expected persistency behaviour
That means you want to know whether an object stores the changes on that
object permanently or not? I am not sure if this is not
implementation-specific.
<bw>
It SHOULD not be implementation specific.
How can a management station manage multiple devices (multiple vendors)
if persistency behaviour of data is unknown? Just trial and error?
</bw>
> - Counter32 objects with no test in the DESCRIPTION clauses about
>  possible discontinuities and which timer object would indicate such.
>  Specifically, the fact that (I think) the ntpd keeps track of the 
> Counters,
>  it seems that there may be discontinuities at other times than when
>  the snmpd restarts (e.g. at other times than reset of sysUpTime)
Not sure what you mean, can you please provide me with an example?

<bw>
COuld there be discontinuities when the ntp deamon restarts?
If so, the management station wants to have a timer-like object to check
if such things occur. See the definition of Counter32 (RFC2578) and/or check
other MIB examples
</bw>

> - I see a whole list of REVISION clauses. Normally we only have a
>  single revision clause at RFC publication time. Not a list of revisions
>  that took place during I-D revisions.
OK.
> - I am missing the Copyright statement in the DESCRIPTION clause
>  of the MODULE_IDENTITY
I guess this has been overseen but can be added quite easily. Where can
I find the required copyright statement in its correct form?

<bw>
I am not 100% sure what it is at this point in time... there was/is a lot
of discussion on this on the IETF list at this time. Check with your WG 
chair(s)
</bw>

> - I am missing that this revision of the document is published as RFC xxxx
>  (xxxx to be filled in by RFC-editor)
OK.
> - I see a lot of objects with a SYNTAX of DisplayString.
>  I would like to point out "note 2" on web page
>       http://www.ops.ietf.org/mib-common-tcs.html
>   Note 2.  DisplayString does not support internationalized text.
>            It MUST NOT be used for objects that are required to
>            hold internationalized text (which is always the case
>            if the object is intended for use by humans [RFC2277]).
>            Designers SHOULD consider using SnmpAdminString,
>            Utf8String, or LongUtf8String for such objects.
The DisplayString objects are mainly used for values which require to be
floating point and we agreed in the working group discussions that it
would make sense to use a string instead that can be converted into an
fp value by a machine.

<bw>
I suggest you describe this at some place in your document; possibly as a 
comment
in your MIB module. Even then, I am not sure if this is wise. I will check 
with
other MIB doctors (in fact they are copied on this email).
But I also see many non FP objects that use DisplayString (for as far as I 
can tell no
good reason).
</bw>

> - Instead of
>     ntpEntNotifPrefix  OBJECT IDENTIFIER ::= { ntpSnmpMIBObjects 6 }
>     ...
>     ntpEntNotifications OBJECT IDENTIFIER ::= { ntpEntNotifPrefix 0 }
>
>  I propose/suggest to do
>     ntpEntNotifications OBJECT IDENTIFIER ::= { ntpSnmpMIB 0 }
>
>  This makes it more inline with what we often do in MIB module.
>  Also makes the OIDs of notifications shorter
OK, agreed.
> - I strongly recommend to use the MIB structure as per RFC4181,
>  which suggests that you would replace
>       ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 6 }
>  with
>       ntpEntConformance OBJECT IDENTIFIER ::= { ntpSnmpMIB 2 }
>
OK.
> - I see OBJECT-GROUP definitions like
>   ntpEntObjectsGroup1 OBJECT-GROUP
>      OBJECTS {
>              ntpEntSoftwareName,
>              ntpEntSoftwareVersion,
>              ntpEntSoftwareVersionVal,
>              ntpEntSoftwareVendor,
>              ntpEntSystemType,
>              ntpEntStatusEntityUptime,
>              ntpEntStatusDateTime,
>              ntpAssocName,
>              ntpAssocRefId,
>
>              ntpAssocAddressType,
>              ntpAssocAddress
>     }
>     STATUS      current
>     DESCRIPTION
>         "A collection of objects for the NTP MIB that all NTP
>          or SNTP entities should implement."
>     ::= { ntpEntGroups 1 }
>
>  Text about "should implement" or "optional" or such is NOT supposed to be
>  in an OBJECT-GROUP DESCRIPTION clause. The OBJECT-GROUP is
>  only meant to group objects logically together.
>  If such a group is mandatory or optional is something that is expressed
>  via MANDATORY-GROUPS or via the GROUP clauses in the
>  MODULE-COMPLIANCE.
OK, I will remove the text from the description and change the group
clauses accordingly.
> As another example, you have
>
>     ntpEntObjectsGroup2 OBJECT-GROUP
>     ...
>     DESCRIPTION
>        "A collection of objects for the NTP MIB that are optional
>         for NTP or SNTP entities to implement."
>     ::= { ntpEntGroups 2 }
>
>  So here you say that the group is optional while you have listed this 
> group
>  as a MANDATORY-GROUP here:
>
>    ntpEntNTPCompliance MODULE-COMPLIANCE
>       STATUS      current
>       DESCRIPTION
>          "The compliance statement for SNMP entities which use NTP and
>           implement the NTP MIB"
>      MODULE  -- this module
>          MANDATORY-GROUPS {
>                           ntpEntObjectsGroup1,
>                           ntpEntObjectsGroup2,
>                           ntpEntNotifPrefixGroup
>         }
>         ::= { ntpEntCompliances 1 }
>
>  So that is a conflict in your MIB-Module.
OK.
> - I see a lot of MIB-level comment lines, aka:
>
>  ntpEntSoftwareVersion OBJECT-TYPE
>    SYNTAX      DisplayString
>    MAX-ACCESS  read-only
>    STATUS      current
>    DESCRIPTION
>        "The software version of the installed NTP implementation."
>    -- full version string, e.g. "ntpd-4.2.0b@1.1433 ..."
>    ::= { ntpEntInfo  2 }
>
>   I think it is much better to include that informatrion in the 
> DESCRIPTION
>   clauses. Otherwise it will often be lost when the MIB module is 
> extracted
>   or used as input for generating help text etc.
Good point, noted.
> - I see references/citations aka:
>
> NtpDateTime ::= TEXTUAL-CONVENTION
>    DISPLAY-HINT "4d:4d:4d.4d"
>    STATUS      current
>    DESCRIPTION
>        "NTP date/time on the device, in 128-bit
>         NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06,
>         section 6:
>          It includes a 64-bit signed seconds field
>          spanning 584 billion years and a 64-bit fraction
>          field resolving .05 attosecond (i.e. 0.5e-18).
>          For convenience in mapping between formats, the
>          seconds field is divided into a 32-bit era field
>          and a 32-bit timestamp field.
>
>         If time is not syncronized this field shall be a
>         zero-length string.
>
>         This TC is not to be used for objects that are used
>         to set the time of the node querying this object.
>
>         NTP should be used for this--or at least SNTP."
>    SYNTAX      OCTET STRING (SIZE (0 | 16))
>
>  I suggest that the pointer to Ref: draft-ietf-ntp-ntpv4-proto-06
>  is changed to Ref: RFC yyyy (and ask RFC-editor to fill in
>  that yyyy value. I see that Ref: draft-ietf-ntp-ntpv4-proto-11 is
>  also in Last Call, so that would be fine.
>  In genreal though, it is probably better to use the REFERENCE
>  clause. So it would be something like
>
>    REFERENCE   "Network Time Protocol Version 4 Protocol
>                                 And Algorithms Specification, sect 6, RFC 
> yyyy"
>
OK, makes perfect sense.
> - It seems to me that for something like this:
>   ntpEntStatusEntityUptime OBJECT-TYPE
>      SYNTAX      Unsigned32
>      MAX-ACCESS  read-only
>      STATUS      current
>      DESCRIPTION
>          "The uptime of the NTP entity in seconds."
>      -- time since ntpd was (re-)started (not sysUptime!)
>      DEFVAL { 0 }
>      ::= { ntpEntStatus 9 }
>
>  I would add a  UNITS clause.
>  I would also move the comment line inside the DESCRIPTION clause.
>  I am not sure if a DEFVAL of 0 (zero) makes sense.
>  Specifically... what would the value be if the snmp agent has started
>  later that ntpd? What if the snmp agent restarts and the ntpd does not?
>  In fact, I think that a DEFVAL clause makes no sense for this object.
Agreed, I will remove the DEFAL line. Can you provide me with an example
on how to use the UNITS clause?

<bw>
   ntpEntStatusEntityUptime OBJECT-TYPE
       SYNTAX      Unsigned32
       UNITS           "seconds"
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
            "The uptime of the NTP entity in seconds."
           -- time since ntpd was (re-)started (not sysUptime!)

</bw>

>  I in fact wonder if most of the DEFVAL values for the read-only objects
>  make sense.
>
> - For
>  ntpEntStatPktModeTable OBJECT-TYPE
>    SYNTAX           SEQUENCE OF NtpEntStatPktModeEntry
>    MAX-ACCESS       not-accessible
>    STATUS           current
>    DESCRIPTION
>        "The number of packets sent and received by packet mode."
>    ::= { ntpEntStatus 18 }
>
>  ntpEntStatPktModeEntry OBJECT-TYPE
>    SYNTAX      NtpEntStatPktModeEntry
>    MAX-ACCESS  not-accessible
>
>    STATUS      current
>    DESCRIPTION
>        "The number of packets sent and received by packet mode."
>    INDEX       { ntpEntStatPktMode }
>    ::= { ntpEntStatPktModeTable 1 }
>
>  I am surprised by the SAME DESCRIPTION clause for each of these!!??
I will change that.
> - When I see:
> ntpAssocAddressType OBJECT-TYPE
>    SYNTAX      InetAddressType
>    MAX-ACCESS  read-only
>    STATUS      current
>    DESCRIPTION
>        "The type of address of the association."
>    -- contains the type of address for uni/multi/broadcast associations
>    ::= { ntpAssociationEntry 4 }
>
> ntpAssocAddress OBJECT-TYPE
>    SYNTAX      InetAddress
>    MAX-ACCESS  read-only
>    STATUS      current
>    DESCRIPTION
>        "The IP address (IPv4 or IPv6) of the association."
>    -- contains IP address of uni/multi/broadcast associations
>    ::= { ntpAssociationEntry 5 }
>
>  Then I like to point out that RFC4001 states that the use of InetAddress
>  SYNTAX, MUST have a DESCRIPTION clause that explain./states
>  which object of SYNTAX InetAddressType controls the format of
>  the InetAddress object. It is most probably ntpAssocAddressType
>  but it would be good to state so.
>
>  Besides, if you are sure that this ALWAYS only applies to IPv4 and IPv6,
>  then I would do it as follows:
>
>    ntpAssocAddressType OBJECT-TYPE
>       SYNTAX      InetAddressType { ipv4, ipv6 }
>
>   ntpAssocAddress OBJECT-TYPE
>       SYNTAX      InetAddress SIZE(4|16)
>
Thanks, I will do it this way because we currently only have NTP over
IPv4 and IPv6 - to my knowledge.
> You must check if you also want to use Zoned addressed, because then
>  that must be added too.
Any thoughts on that by anybody?
> If, at the other hand, other values than ipv4/ipv6 are possible (maybe
> in the future?) then it might be better to put the "minimum support for
> ipv4/ipv6 requirement in the MODULE-COMPLIANCE via an OBJECT
> and SYNTAX clause.
Again, since this is my first MIB I would appreciate an example.

<bw>
Look for example at the MODULE-COMPLIANCE for rfc3289; here is an extract:
    OBJECT diffServMultiFieldClfrAddrType
    SYNTAX  InetAddressType { unknown(0), ipv4(1), ipv6(2) }
    DESCRIPTION
       "An implementation is only required to support IPv4 and IPv6
       addresses."

    OBJECT diffServMultiFieldClfrDstAddr
    SYNTAX  InetAddress (SIZE(0|4|16))
    DESCRIPTION
       "An implementation is only required to support IPv4 and globally
       unique IPv6 addresses."

</bw>

>
> - I see some 8 notifications. Is there a risk that too many get generated
>  at any point in time, such that it would flood the network and/or
>  overload a NMS ??
>  It would be good to add some text about the expected max notification
>  rates and/or add a throthle or an enable/disable switch.
OK, I will look into this.
> - It seems that RFC4001 is missing as a normative reference.
OK.
> - I would think that the new draft-ietf-ntp-ntpv4-proto-11 (version 4 of 
> NTP)
>  should also be a normative reference
Shouldn't we use the RFC yyyy approach instead (yyyy being the
to-be-assigned RFC for the protocol RFC)?

<bw> yes please</bw>

> - The security section is not according to the guidelines provided at
>       http://www.ops.ietf.org/mib-security.html
I unfortunately currently seem to be unable to access this website (and
www.ietf.org as well), but I think it would be helpful to know which
points are missing / wrong in your oppinion.

<bw>
basically all of it. Pls try again when you can access the web site
</bw>

>
> - I have not checked the new NTP version 4 spec to see if the 
> knobs/sensors
>  in that protocol have properly been modeled in this MIB module.
>  That is a separate task that may actually need much more time than the
>  review I have done for now.
Since this has been discussed in the working group I would expect that
everybody is happy with what is in the MIB right now.

<bw>
That may be the case, but given the many basic concerns I raise, that does 
not
give me a warm feeling.
</bw>

But I really
appreciate your efforts and your very detailed review of this document.
I only wish we would have somebody sending me such a review earlier in
the process, before everything went into last call.

<bw>
Basically WG chairs can/should know that they can ask for MIB doctor help
early in the process. And as far as I knopw, Chris is well aware of that 
too.
</bw>

Anyway, you did a
great job and I think this was a very useful review. I will go back to
my drawing desk and start to implement the advised changes.

Best Regards,
  Heiko

> Bert Wijnen 

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Wed Feb 25 08:11:27 2009
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2C0528C10E for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed, 25 Feb 2009 08:11:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yemvhZ6W2bkh for <ietfarch-ntp-archives-ahFae6za@core3.amsl.com>; Wed, 25 Feb 2009 08:11:26 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [204.152.184.126]) by core3.amsl.com (Postfix) with ESMTP id A2CC828C0F8 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 25 Feb 2009 08:11:23 -0800 (PST)
Received: from ntp1.isc.org (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id B231B39FC2 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 25 Feb 2009 16:11:42 +0000 (UTC) (envelope-from ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org)
X-Original-To: ntpwg@lists.ntp.isc.org
Delivered-To: ntpwg@lists.ntp.isc.org
Received: from localhost (localhost [127.0.0.1]) by mail1.ntp.org (Postfix) with ESMTP id 5A28239F8C for <ntpwg@lists.ntp.isc.org>; Wed, 25 Feb 2009 16:10:58 +0000 (UTC) (envelope-from brian@innovationslab.net)
Received: from mail1.ntp.org ([127.0.0.1]) by localhost (ntp1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31083-05 for <ntpwg@lists.ntp.isc.org>; Wed, 25 Feb 2009 16:10:55 +0000 (UTC)
X-Greylist: delayed 942 seconds by postgrey-1.21 at ntp1.isc.org; Wed, 25 Feb 2009 16:10:54 UTC
Received: from jhuapl.edu (pilot.jhuapl.edu [128.244.198.200]) by mail1.ntp.org (Postfix) with ESMTP for <ntpwg@lists.ntp.isc.org>; Wed, 25 Feb 2009 16:10:18 +0000 (UTC) (envelope-from brian@innovationslab.net)
Received: from ([128.244.206.11]) by pilot.jhuapl.edu with ESMTP with TLS id 5502123.136587300; Wed, 25 Feb 2009 10:54:07 -0500
Message-ID: <49A5699F.7070600@innovationslab.net>
Date: Wed, 25 Feb 2009 10:54:07 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <3EF7C2B482804D15A054261F369CBFCB@BertLaptop>	<499D081D.7020109@meinberg.de> <A66203920E184B50B2C91DD7BC9D7D93@BertLaptop>
In-Reply-To: <A66203920E184B50B2C91DD7BC9D7D93@BertLaptop>
Cc: ntpwg@lists.ntp.isc.org, chelliot@pobox.com
Subject: Re: [ntpwg] My review of: draft-ietf-ntp-ntpv4-mib-05.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <https://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <https://lists.ntp.org/mailman/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Inline...

Bert Wijnen (IETF) wrote:

<snip>

>> - writable objects for which I see no text in the DESCRIPTION clauses
>>  about expected persistency behaviour
> That means you want to know whether an object stores the changes on that
> object permanently or not? I am not sure if this is not
> implementation-specific.
> <bw>
> It SHOULD not be implementation specific.
> How can a management station manage multiple devices (multiple vendors)
> if persistency behaviour of data is unknown? Just trial and error?
> </bw>
>> - Counter32 objects with no test in the DESCRIPTION clauses about
>>  possible discontinuities and which timer object would indicate such.
>>  Specifically, the fact that (I think) the ntpd keeps track of the 
>> Counters,
>>  it seems that there may be discontinuities at other times than when
>>  the snmpd restarts (e.g. at other times than reset of sysUpTime)
> Not sure what you mean, can you please provide me with an example?
> 
> <bw>
> COuld there be discontinuities when the ntp deamon restarts?
> If so, the management station wants to have a timer-like object to check
> if such things occur. See the definition of Counter32 (RFC2578) and/or check
> other MIB examples
> </bw>

As an example of how the UDP MIB deals with discontinuities, take a look 
at the udpInDatagrams object (and other Counter32 objects) in RFC 4113.

> 
>> - I see a whole list of REVISION clauses. Normally we only have a
>>  single revision clause at RFC publication time. Not a list of revisions
>>  that took place during I-D revisions.
> OK.
>> - I am missing the Copyright statement in the DESCRIPTION clause
>>  of the MODULE_IDENTITY
> I guess this has been overseen but can be added quite easily. Where can
> I find the required copyright statement in its correct form?
> 
> <bw>
> I am not 100% sure what it is at this point in time... there was/is a lot
> of discussion on this on the IETF list at this time. Check with your WG 
> chair(s)
> </bw>

I believe the following is the correct text to include in the 
DESCRIPTION clause:

    Copyright (c) 2009 IETF Trust and the persons identified as the
    document authors.  All rights reserved.

    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
    carefully, as they describe your rights and restrictions with respect
    to this document.

<snip>

>> - When I see:
>> ntpAssocAddressType OBJECT-TYPE
>>    SYNTAX      InetAddressType
>>    MAX-ACCESS  read-only
>>    STATUS      current
>>    DESCRIPTION
>>        "The type of address of the association."
>>    -- contains the type of address for uni/multi/broadcast associations
>>    ::= { ntpAssociationEntry 4 }
>>
>> ntpAssocAddress OBJECT-TYPE
>>    SYNTAX      InetAddress
>>    MAX-ACCESS  read-only
>>    STATUS      current
>>    DESCRIPTION
>>        "The IP address (IPv4 or IPv6) of the association."
>>    -- contains IP address of uni/multi/broadcast associations
>>    ::= { ntpAssociationEntry 5 }
>>
>>  Then I like to point out that RFC4001 states that the use of InetAddress
>>  SYNTAX, MUST have a DESCRIPTION clause that explain./states
>>  which object of SYNTAX InetAddressType controls the format of
>>  the InetAddress object. It is most probably ntpAssocAddressType
>>  but it would be good to state so.
>>
>>  Besides, if you are sure that this ALWAYS only applies to IPv4 and IPv6,
>>  then I would do it as follows:
>>
>>    ntpAssocAddressType OBJECT-TYPE
>>       SYNTAX      InetAddressType { ipv4, ipv6 }
>>
>>   ntpAssocAddress OBJECT-TYPE
>>       SYNTAX      InetAddress SIZE(4|16)
>>
> Thanks, I will do it this way because we currently only have NTP over
> IPv4 and IPv6 - to my knowledge.
>> You must check if you also want to use Zoned addressed, because then
>>  that must be added too.
> Any thoughts on that by anybody?

I believe we would need scoped (or zoned) addresses *if* there are 
deployment scenarios where an NTP speaker is associated with multiple 
peers in different limited-scoped networks.  For example, can I have one 
NTP association with node1 via a site-local IPv6 multicast address in a 
VPN connection and another association with node2 via the same 
site-local IPv6 multicast address over a different interface?

If the answer is "yes", then we need to support the scoped (zoned) 
addresses.

Regards,
Brian
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/ntpwg
