[93605] in North American Network Operators' Group
Re: anycasting behind different ASNs?
daemon@ATHENA.MIT.EDU (Deepak Jain)
Wed Dec 6 17:44:36 2006
Date: Wed, 06 Dec 2006 17:23:03 -0500
From: Deepak Jain <deepak@ai.net>
Reply-To: deepak@ai.net
To: Steve Gibbard <scg@gibbard.org>
Cc: John Kristoff <jtk@ultradns.net>, nanog@merit.edu
In-Reply-To: <20061206111430.Y23771@sprockets.gibbard.org>
Errors-To: owner-nanog@merit.edu
> An easy way around this is to be consistent about your transit and
> peering arrangements across locations. If your anycast network has
> transit from a network in one location, get transit from them in your
> other locations, and let hot potato routing do its thing. For cases
> where this isn't practical, or where you want more control over who is
> sending traffic to a node, declare the node to be a "peering only" node
> and make sure your peers aren't leaking the anycast routes to their out
> of region upstreams.
>
Or prepend (gasp!) like the Dickens for your "peering only" node to have
transit, but be the route chosen after transit/connectivity to your
"transit/peering ok" node fails.
Deepak
