IETF Logo Mail Archive

Re: [Ntp] Antw: [EXT] Re: Timescales

Miroslav Lichvar <mlichvar@redhat.com> Wed, 09 December 2020 13:46 UTC

Return-Path: <mlichvar@redhat.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47DB13A1675 for <ntp@ietfa.amsl.com>; Wed, 9 Dec 2020 05:46:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52eF0dEAwUpr for <ntp@ietfa.amsl.com>; Wed, 9 Dec 2020 05:46:23 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 493403A1672 for <ntp@ietf.org>; Wed, 9 Dec 2020 05:46:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1607521582; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=LOC+xefaqa4t1to1v0URKt9YOHf0zkepfw2BoffrsV8=; b=SpxoMyLhxcdzpMtjTxCMS07JVxCP/w/iKT3aXFs78gW0mzEH/3yAtra9bzagq7qf2tLEqX nmIC8eLmXvUaOCLeiZ9aYRML6veKN5i/miXoEzBP/9Ai9egYczO4e7pgi4ZSyU1j8hLljj sRpyi8z7expMA3UKaOrq982F3sXipsI=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-574-HTCoAgbeMG2XMJl14N6gIQ-1; Wed, 09 Dec 2020 08:46:19 -0500
X-MC-Unique: HTCoAgbeMG2XMJl14N6gIQ-1
Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E2B0A190A7DE; Wed, 9 Dec 2020 13:46:15 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2A17C1045D06; Wed, 9 Dec 2020 13:46:13 +0000 (UTC)
Date: Wed, 09 Dec 2020 14:46:12 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: Hal Murray <hmurray@megapathdsl.net>, "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <20201209134612.GC2352378@localhost>
References: <20201209101830.7CB0240605C@ip-64-139-1-69.sjc.megapath.net> <20201209113003.GA2352378@localhost> <5FD0D13C020000A10003D6CB@gwsmtp.uni-regensburg.de>
MIME-Version: 1.0
In-Reply-To: <5FD0D13C020000A10003D6CB@gwsmtp.uni-regensburg.de>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/rVceeWLguyvCWtxBwg1kOgt551s>
Subject: Re: [Ntp] Antw: [EXT] Re: Timescales
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Dec 2020 13:46:25 -0000

On Wed, Dec 09, 2020 at 02:29:32PM +0100, Ulrich Windl wrote:
> However you could see the leap indication flag also as "leap confirmation"
> flag (actually there will be a leap event). With only DCF-77 clocks this could
> be a problem. As said earlier, it would be best if NTP could reliably transfer
> the leapsecond table, or at least the relevant part of it to make clients know
> in advance that and when a leap event is scheduled.

There is the tzdist (RFC7808) protocol designed for that.

NTP could distribute a leap-second table (it already did it with
Autokey, right?), but isn't NTP about distributing current time,
rather than reconstructing time in the past or future?

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email