IETF Logo Mail Archive

Re: [Ntp] NTPv5 and anycasting

Miroslav Lichvar <mlichvar@redhat.com> Wed, 02 December 2020 08:08 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 6F5E93A011B for <ntp@ietfa.amsl.com>; Wed, 2 Dec 2020 00:08:48 -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_H4=-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 h4-dmhSIVg_O for <ntp@ietfa.amsl.com>; Wed, 2 Dec 2020 00:08:46 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.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 696003A003E for <ntp@ietf.org>; Wed, 2 Dec 2020 00:08:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606896525; 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=eDP/6XeJXyz3P/CIK9IS+67IB0hpZjjhUNw0NwPsB54=; b=H5/n8l/XqAdje5GIxtw6wBGXr+wLOi5X2ps871g8bov/fWH8jO6rb1I19f1mCrO2VhQTkL f4izKBg4FIyJA96k764vtOcRUQelHyjXC+xHHJAkZ0OhLX1YvlBGbpa1IeQpa8/js6QZfP jo7r6QnkPPPsKexPDPPKrAB2JFJNmno=
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-192--JJXKmgzPkqxN1thvIU7CA-1; Wed, 02 Dec 2020 03:08:43 -0500
X-MC-Unique: -JJXKmgzPkqxN1thvIU7CA-1
Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 78B221006C81; Wed, 2 Dec 2020 08:08:42 +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 C88EF10013BD; Wed, 2 Dec 2020 08:08:41 +0000 (UTC)
Date: Wed, 02 Dec 2020 09:08:39 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Philip Prindeville <philipp@redfish-solutions.com>
Cc: "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <20201202080839.GO1900232@localhost>
References: <F2AD65AD-3403-486E-AEF9-3EF07F88A7FF@redfish-solutions.com>
MIME-Version: 1.0
In-Reply-To: <F2AD65AD-3403-486E-AEF9-3EF07F88A7FF@redfish-solutions.com>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22
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/wHfylYEtv0zn2w3tmZTMgKllJRg>
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 08:08:48 -0000

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. 

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email