Re: [Ntp] NTPv5 and anycasting
Kurt Roeckx <kurt@roeckx.be> Thu, 03 December 2020 22:42 UTC
Return-Path: <kurt@roeckx.be>
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 B27423A0DF7 for <ntp@ietfa.amsl.com>; Thu, 3 Dec 2020 14:42:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 kjjydzik6gLG for <ntp@ietfa.amsl.com>; Thu, 3 Dec 2020 14:42:19 -0800 (PST)
Received: from excelsior.roeckx.be (excelsior.roeckx.be [195.234.45.115]) (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 9D8D83A0DEF for <ntp@ietf.org>; Thu, 3 Dec 2020 14:42:19 -0800 (PST)
Received: from intrepid.roeckx.be (localhost [127.0.0.1]) by excelsior.roeckx.be (Postfix) with ESMTP id 378F5A8A0150; Thu, 3 Dec 2020 22:42:17 +0000 (UTC)
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id DA70E1FE0DE0; Thu, 3 Dec 2020 23:42:16 +0100 (CET)
Date: Thu, 03 Dec 2020 23:42:16 +0100
From: Kurt Roeckx <kurt@roeckx.be>
To: Philip Prindeville <philipp@redfish-solutions.com>
Cc: "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <X8lpyD3ToZnrhBUd@roeckx.be>
References: <F2AD65AD-3403-486E-AEF9-3EF07F88A7FF@redfish-solutions.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <F2AD65AD-3403-486E-AEF9-3EF07F88A7FF@redfish-solutions.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/x6z41qvXaeYKKhdWFqgUNmMpL0E>
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: Thu, 03 Dec 2020 22:42:22 -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. I don't see how anycast changes anything at all. It's true that because of routing changes that the RTT might change, but that's not different then any other route change. The only thing that's really different is that because of routing changes you might actually talk to a different server, but without anycast you can also talk to a different server each time because there is a load balancer in between. And NTP should deal with all those without any problem. Kurt
- [Ntp] NTPv5 and anycasting Philip Prindeville
- Re: [Ntp] NTPv5 and anycasting Miroslav Lichvar
- Re: [Ntp] NTPv5 and anycasting Philip Prindeville
- Re: [Ntp] NTPv5 and anycasting Paul Gear
- Re: [Ntp] NTPv5 and anycasting Steven Sommars
- Re: [Ntp] NTPv5 and anycasting Philip Prindeville
- Re: [Ntp] NTPv5 and anycasting Watson Ladd
- Re: [Ntp] NTPv5 and anycasting Denis Reilly
- Re: [Ntp] NTPv5 and anycasting Philip Prindeville
- Re: [Ntp] NTPv5 and anycasting Kurt Roeckx
- Re: [Ntp] NTPv5 and anycasting Miroslav Lichvar