IETF Logo Mail Archive

Re: [Ntp] An NTPv5 design sketch

Miroslav Lichvar <mlichvar@redhat.com> Thu, 16 April 2020 16:37 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 63D383A0E41 for <ntp@ietfa.amsl.com>; Thu, 16 Apr 2020 09:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.268
X-Spam-Level:
X-Spam-Status: No, score=-2.268 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 cFL4q4ZPQ3Ab for <ntp@ietfa.amsl.com>; Thu, 16 Apr 2020 09:37:01 -0700 (PDT)
Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [205.139.110.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 555CD3A0E3F for <ntp@ietf.org>; Thu, 16 Apr 2020 09:37:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587055020; 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=+H0jKjB6ZBc+ZBWgb9kJQwz9QZnakajS8Xjw+gWmRI4=; b=dqjYs6VHxUlLON3HsKmVNnZAIQowc5wBF4QoJ/fGjj5H9WNMJ08IBMw4DFX/aon58C6ACL fmPkGeG+6ZdriLRcCsSVCuRIkroPF/i938marKaTi5iftwZLegvogGlftTBAlT4wF6DGx8 9tlFeYuJF3TrwxrVdBR3ESLJ7n2ZbcA=
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-32-oWCtsCkXPOOp12WbxpUX-A-1; Thu, 16 Apr 2020 12:36:58 -0400
X-MC-Unique: oWCtsCkXPOOp12WbxpUX-A-1
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id F33AE2F63; Thu, 16 Apr 2020 16:36: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 270775DA7B; Thu, 16 Apr 2020 16:36:55 +0000 (UTC)
Date: Thu, 16 Apr 2020 18:36:54 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Doug Arnold <doug.arnold@meinberg-usa.com>
Cc: Daniel Franke <dfoxfranke@gmail.com>, NTP WG <ntp@ietf.org>
Message-ID: <20200416163654.GK1945@localhost>
References: <CAJm83bBV+Pox3r6KU49ShwMOvr=R+U_vDKJtSZhfT6XX4qWmbA@mail.gmail.com> <20200414112541.GD1945@localhost> <CAJm83bCxuS_X68-pvpOWCPSmjAjTeYNJVuuOEhV-i82R7B28Mg@mail.gmail.com> <20200414155241.GF1945@localhost> <CAJm83bC1EhwQQ=+B7XPbEkvhOWvxU8zjCd290Fj5N43aMJQTkg@mail.gmail.com> <20200415072023.GG1945@localhost> <CAJm83bAEDuLk6vSa82D3smXO4x7iDywoy+FpC=gdm=m3SLrVLg@mail.gmail.com> <20200416082557.GI1945@localhost> <DB8PR02MB5611418689CEA2FB66C0FD80CFD80@DB8PR02MB5611.eurprd02.prod.outlook.com>
MIME-Version: 1.0
In-Reply-To: <DB8PR02MB5611418689CEA2FB66C0FD80CFD80@DB8PR02MB5611.eurprd02.prod.outlook.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/h5WKs_l1duuXqVpC6yYcbv6CI4M>
Subject: Re: [Ntp] An NTPv5 design sketch
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: Thu, 16 Apr 2020 16:37:02 -0000

On Thu, Apr 16, 2020 at 04:11:21PM +0000, Doug Arnold wrote:
> Supporting simple harware implementations in closed specialized networks, like a robot, is a problem already well solved by PTP.  Making NTP do that does not help solve technical problems.  Making a timing protocol that is robust and secure is not at all solved by PTP.  That is how NTPv5 can make the world better.

Better accuracy seems to be one of the goals of the proposed design as
it includes the correction field. I would like to see it in one form
or another included in the spec.

Maybe the best example of an extremely simple device that needs to
support NTPv5 and nothing else is an NTPv5 stratum-1 server. Consider
how much will the cost of the hardware change if NTS is required
and the same performance is expected.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email