IETF Logo Mail Archive

Re: [Ntp] Timescales, leapseconds and smearing

Miroslav Lichvar <mlichvar@redhat.com> Tue, 08 December 2020 09:34 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 10D9F3A074E for <ntp@ietfa.amsl.com>; Tue, 8 Dec 2020 01:34:02 -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_H3=-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 nwVkeLZz0mwP for <ntp@ietfa.amsl.com>; Tue, 8 Dec 2020 01:34:00 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.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 9BCD23A074B for <ntp@ietf.org>; Tue, 8 Dec 2020 01:34:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1607420039; 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=76MZ6EWOoqgnYROFb3RGSFdvEe09yaYJqRaebBqsH7k=; b=goTSVQJVgMbO2ymnr5su2AYsP52UYH0AtYwoqbDp0qdxilQ9jew5RKO7CNVb0tD85f5url /Ig/2iiGdSfPGGQX3HYkpWATSRHCggrPVVe5bD1+nK7ScOHBTPx6BoesnWbO7+2MQZaAF4 i5huctS5dmEPZLuBo6/jk1BQdz7lHxg=
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-357-eW5A1EUGM7qy0QKlC2rxGw-1; Tue, 08 Dec 2020 04:33:57 -0500
X-MC-Unique: eW5A1EUGM7qy0QKlC2rxGw-1
Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 091B0858180; Tue, 8 Dec 2020 09:33:56 +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 36A2560BE2; Tue, 8 Dec 2020 09:33:54 +0000 (UTC)
Date: Tue, 08 Dec 2020 10:33:53 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: Kurt Roeckx <kurt@roeckx.be>, ntp@ietf.org
Message-ID: <20201208093353.GS2352378@localhost>
References: <kurt@roeckx.be> <X86sVykHUqlkXP96@roeckx.be> <20201207234858.47ECE40605C@ip-64-139-1-69.sjc.megapath.net>
MIME-Version: 1.0
In-Reply-To: <20201207234858.47ECE40605C@ip-64-139-1-69.sjc.megapath.net>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12
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/lu4uq8L3Z7mqcWHZvZmuevevMmc>
Subject: Re: [Ntp] Timescales, leapseconds and smearing
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: Tue, 08 Dec 2020 09:34:02 -0000

On Mon, Dec 07, 2020 at 03:48:58PM -0800, Hal Murray wrote:
> > We have various timescales people might care about:
> > - NTP
> 
> Current on-the-wire NTP format is only 32 bits of seconds since start of 
> epoch.  Should we extend that to 64 bits so we never have to worry about 
> epochs?

Making the NTP timestamps 96-bit?

The NTPv5 draft has an 8-bit extension of the receive timestamp, which
covers ~35000 years.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email