Re: [Ntp] NTPv5: big picture

Philip Prindeville <philipp@redfish-solutions.com> Sat, 02 January 2021 02:23 UTC

Return-Path: <philipp@redfish-solutions.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 AC0103A0A2E; Fri, 1 Jan 2021 18:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 kxAgF5D1SPot; Fri, 1 Jan 2021 18:23:03 -0800 (PST)
Received: from mail.redfish-solutions.com (mail.redfish-solutions.com [45.33.216.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F057A3A0A2D; Fri, 1 Jan 2021 18:23:02 -0800 (PST)
Received: from [192.168.3.4] ([192.168.3.4]) (authenticated bits=0) by mail.redfish-solutions.com (8.16.1/8.16.1) with ESMTPSA id 1022N1Z1335648 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 1 Jan 2021 19:23:01 -0700
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Philip Prindeville <philipp@redfish-solutions.com>
In-Reply-To: <1e57c173-d3a9-4621-df47-0e847e837abf@libertysys.com.au>
Date: Fri, 01 Jan 2021 19:23:00 -0700
Cc: ntp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1B09CE2-2FD0-41A7-9173-C0A4FDD2F0C2@redfish-solutions.com>
References: <20210101025440.ECE3340605C@ip-64-139-1-69.sjc.megapath.net> <0DF4D79B-29BA-4DB0-A3D6-EE3B6AE807DF@meinberg-usa.com> <993FEEB5-F498-472E-813E-E684E273612F@akamai.com> <1e57c173-d3a9-4621-df47-0e847e837abf@libertysys.com.au>
To: Paul Gear <ntp=40libertysys.com.au@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Scanned-By: MIMEDefang 2.84 on 192.168.1.3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/715yPZnrH7PGqgoW42nA4r0sT5E>
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: Sat, 02 Jan 2021 02:23:05 -0000

> On Jan 1, 2021, at 6:54 PM, Paul Gear <ntp=40libertysys.com.au@dmarc.ietf.org> wrote:
> 
> It's great to aim for making NTP more suitable for high-accuracy
> environments which can currently only be served by PTP, but we shouldn't
> do this at the cost of making NTPv5 less viable for adoption by those
> billions by making it harder to deploy (e.g. by requiring changes to
> every firewall which allows NTP, or making it hard to work out whether
> you're looking at UTC or TAI time).


I occasionally bang on the default set of rules for OpenWRT, perhaps the most pervasive Open Source router package out there today.  What are your specific concerns about what’s not being done?

The current model for OpenWRT is that it’s a suborned peer to more accurate (lower stratum) servers out there, and then in turn provides time to the clients inside its perimeter.  It typically doesn’t support queries from external sources (which helps avoid spoofing attacks).

If there’s something we’re not doing that we should be, please call it out now.  Or conversely, something we’re doing that we shouldn’t be...

Thanks