[181150] in North American Network Operators' Group
Re: Anycast provider for SMTP?
daemon@ATHENA.MIT.EDU (Joe Abley)
Wed Jun 17 17:29:58 2015
X-Original-To: nanog@nanog.org
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <00f801d0a942$4fbb6040$ef3220c0$@gmail.com>
Date: Wed, 17 Jun 2015 17:27:53 -0400
To: Chuck Church <chuckchurch@gmail.com>
Cc: NANOG list <nanog@nanog.org>, Joe Hamelin <joe@nethead.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jun 17, 2015, at 17:15, Chuck Church <chuckchurch@gmail.com> wrote:
>> As such, you typically only see it leveraged for simple services (e.g. DNS, NTP).
>
> I've been thinking about this for NTP. Wouldn't you end up with constant corrections with NTP and Anycast?
I am not a time geek, but the general and consistent advice I have
heard from actual such geeks is, as you suspected, not to use anycast
to distribute NTP service.
I imagine that advice could be modified somewhat if you differentiate
between NTP as used within a mesh of well-synchronised clocks and NTP
as an occasional service for mobile clients that require only a loose
sense of now. The latter seems like availability might be more
important than stability over an extended period, so anycast might
make sense there.
Joe
