[93606] in North American Network Operators' Group
Re: anycasting behind different ASNs?
daemon@ATHENA.MIT.EDU (Steve Gibbard)
Wed Dec 6 18:08:12 2006
Date: Wed, 6 Dec 2006 14:40:07 -0800 (PST)
From: Steve Gibbard <scg@gibbard.org>
To: Deepak Jain <deepak@ai.net>
Cc: John Kristoff <jtk@ultradns.net>, nanog@merit.edu
In-Reply-To: <457742C7.6070509@ai.net>
Errors-To: owner-nanog@merit.edu
On Wed, 6 Dec 2006, Deepak Jain wrote:
>
>> 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.
Doesn't work. Local preference gets considered before AS path.
-Steve
