[76605] in North American Network Operators' Group
Re: Anycast 101
daemon@ATHENA.MIT.EDU (Michael.Dillon@radianz.com)
Fri Dec 17 09:17:42 2004
In-Reply-To: <03ABCE4F-5024-11D9-B673-000A95CD987A@muada.com>
To: nanog@merit.edu
From: Michael.Dillon@radianz.com
Date: Fri, 17 Dec 2004 14:16:58 +0000
Errors-To: owner-nanog-outgoing@merit.edu
> That's not the point. If without anycast this is better than with
> anycast, then this should go on the "con" list for anycast.
People often confuse two separate technical things
here. One is the BGP anycast technique which allows
anycasting to be used in an IPv4 network, and the
other is the application of BGP anycasting to DNS
in an IPv4 network. It would be clearer if people
would prefix "anycast" with either BGP or DNS to make
it clear which they are talking about. Conceivably
there could be other applications that could be
distributed using BGP anycast. And if those applications
are designed knowing the quirks of BGP anycasting
then presumably they would have ways to overcome
some of the issues that affect DNS.
I would reword your statement as follows.
... then this should go on the "con" list for
DNS anycasting.
--Michael Dillon
