IETF Logo Mail Archive

Re: [Ntp] NTPv5 and anycasting

Philip Prindeville <philipp@redfish-solutions.com> Wed, 02 December 2020 17:48 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 90BDD3A14E6 for <ntp@ietfa.amsl.com>; Wed, 2 Dec 2020 09:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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] 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 NALD1PmALbTs for <ntp@ietfa.amsl.com>; Wed, 2 Dec 2020 09:48:55 -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 3CCA63A14EA for <ntp@ietf.org>; Wed, 2 Dec 2020 09:48:45 -0800 (PST)
Received: from [192.168.3.4] (67-42-76-224.bois.qwest.net [67.42.76.224] (may be forged)) (authenticated bits=0) by mail.redfish-solutions.com (8.16.1/8.16.1) with ESMTPSA id 0B2HmhCH088385 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 2 Dec 2020 10:48:43 -0700
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
From: Philip Prindeville <philipp@redfish-solutions.com>
In-Reply-To: <20201202080839.GO1900232@localhost>
Date: Wed, 02 Dec 2020 10:48:43 -0700
Cc: "ntp@ietf.org" <ntp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CAE44A6-41A6-4516-8CD1-217C87C28E47@redfish-solutions.com>
References: <F2AD65AD-3403-486E-AEF9-3EF07F88A7FF@redfish-solutions.com> <20201202080839.GO1900232@localhost>
To: Miroslav Lichvar <mlichvar@redhat.com>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
X-Scanned-By: MIMEDefang 2.84 on 192.168.1.3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ELss3MiwRfftrZmxAB7BgMv-hiQ>
Subject: Re: [Ntp] NTPv5 and anycasting
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, 02 Dec 2020 17:48:57 -0000


> On Dec 2, 2020, at 1:08 AM, Miroslav Lichvar <mlichvar@redhat.com> wrote:
> 
> On Tue, Dec 01, 2020 at 10:41:01PM -0700, Philip Prindeville wrote:
>> Sorry if this has been discussed already, but do we want to have a specific prohibition against the use of anycasting with NTPv5?
>> 
>> I can’t see the point in sending packets non-deterministically to one of possibly many servers with different clock values, RTT’s, etc.
> 
> There is a section on anycast in the NTP BCP document. It can be
> useful. I don't see a reason why NTPv5 specifically should prohibit
> use of anycast. 
> 


What’s the scenario where non-determinism is a good thing?

v2.23.0 | Report a Bug | By Email