IETF Logo Mail Archive

Re: [Ntp] NTPv5 and anycasting

Miroslav Lichvar <mlichvar@redhat.com> Mon, 07 December 2020 10: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 0ECA53A12CC for <ntp@ietfa.amsl.com>; Mon, 7 Dec 2020 02:34:30 -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 IwqjpFcd9f2D for <ntp@ietfa.amsl.com>; Mon, 7 Dec 2020 02:34:28 -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 67CB23A12C9 for <ntp@ietf.org>; Mon, 7 Dec 2020 02:34:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1607337267; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bKCvSmI8Xqvz0XjNgq15CruikvozAv2FqB9fAhAYWMk=; b=Fvr9wO5D8oQzOwG1rAGjLKX0YFwKx+foiVjt5+OdVTOKoj5yb2Xm/PqlDl5773Srzw1PSC L05HEcYO9jlacQGjMXCWQEXz71ZKAOSNR5Wj9NKKVLdzIPaPOIo1ry6hmFPFL4Xeyr+RaQ 5FdA5yMuulSe3hQXckSUTQ3bksUF1zo=
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-133-gZh52zzpMFq73PB6xe-GuA-1; Mon, 07 Dec 2020 05:34:25 -0500
X-MC-Unique: gZh52zzpMFq73PB6xe-GuA-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 94075858180 for <ntp@ietf.org>; Mon, 7 Dec 2020 10:34:24 +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 19F9B5D9DC for <ntp@ietf.org>; Mon, 7 Dec 2020 10:34:23 +0000 (UTC)
Date: Mon, 07 Dec 2020 11:34:24 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: ntp@ietf.org
Message-ID: <20201207103424.GD2352378@localhost>
References: <F2AD65AD-3403-486E-AEF9-3EF07F88A7FF@redfish-solutions.com> <20201202080839.GO1900232@localhost> <6CAE44A6-41A6-4516-8CD1-217C87C28E47@redfish-solutions.com>
MIME-Version: 1.0
In-Reply-To: <6CAE44A6-41A6-4516-8CD1-217C87C28E47@redfish-solutions.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
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/-f1StsJMH4KQuG9ZXwzGyGnLO28>
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: Mon, 07 Dec 2020 10:34:30 -0000

On Wed, Dec 02, 2020 at 10:48:43AM -0700, Philip Prindeville wrote:
> 
> 
> > 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?

Probably none. I was responding to the first sentence about
prohibiting anycast in general.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email