Re: [Ntp] NTPv5: big picture

Miroslav Lichvar <mlichvar@redhat.com> Tue, 05 January 2021 09:17 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 888D33A0365 for <ntp@ietfa.amsl.com>; Tue, 5 Jan 2021 01:17:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.37
X-Spam-Level:
X-Spam-Status: No, score=-2.37 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, 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 DI08hyqjeJ8Y for <ntp@ietfa.amsl.com>; Tue, 5 Jan 2021 01:17:54 -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 BD1643A02BD for <ntp@ietf.org>; Tue, 5 Jan 2021 01:17:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1609838273; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sdECMiekc/2+2EJdX6Ztrm5OIPxde7/h9tb0XHVCoZo=; b=ACySb8WiLZB5MB83BT4YdPx4gi7fLbj0O3pwldHjKFzDnycXeetI+ELHqEnorCgZnLZQ+P ksGrpGlpeBMwSmI/ex3fWKs7uQw059pdzGcUbgl/UgnDP3SyNti0MDdt7Q/CSYWCJ/sGZy 7fHmwUtV6uUmn0UmRiAqb814J9mZeXY=
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-495-_ynuCoHmPWSqIcidW_yrUw-1; Tue, 05 Jan 2021 04:17:49 -0500
X-MC-Unique: _ynuCoHmPWSqIcidW_yrUw-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 5C3E9107ACE3; Tue, 5 Jan 2021 09:17:48 +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 743FF60BE5; Tue, 5 Jan 2021 09:17:47 +0000 (UTC)
Date: Tue, 05 Jan 2021 10:17:45 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Philip Prindeville <philipp@redfish-solutions.com>
Cc: NTP WG <ntp@ietf.org>, Hal Murray <hmurray@megapathdsl.net>
Message-ID: <20210105091745.GD3008666@localhost>
References: <20210101025440.ECE3340605C@ip-64-139-1-69.sjc.megapath.net> <20210104151813.GB2992437@localhost> <2A05A663-2E81-4B82-973D-E01846EE5C9E@redfish-solutions.com>
MIME-Version: 1.0
In-Reply-To: <2A05A663-2E81-4B82-973D-E01846EE5C9E@redfish-solutions.com>
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="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/gwwJ5KlXTCTN5i6XM3JKyuwtiUI>
Subject: Re: [Ntp] NTPv5: big picture
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, 05 Jan 2021 09:17:57 -0000

On Mon, Jan 04, 2021 at 12:39:41PM -0700, Philip Prindeville wrote:
> I don’t subscribe to this line of reasoning.  It sounds a lot like getting the camel’s nose under the tent for justifying why leap information needs to be part of the protocol.  It doesn’t.  It’s an ugly vestige that should be jettisoned.

It's ugly, but we need NTPv5 to be based in reality and be useful.
The TAI-UTC offset is not always known and clocks are sometimes
synchronized in isolated networks.

> If we used strictly monotonic timestamps, and had a well understood mechanism for mapping from that to any other required format out-of-band, that would be more than adequate: it would be ideal.

Yes, that would be nice, but it's not possible if we want to support
existing use cases of NTP and be implementable on current operating
systems.

-- 
Miroslav Lichvar