[40457] in North American Network Operators' Group
RE: Static routes in an AS vs BGP advertised routes
daemon@ATHENA.MIT.EDU (Brandon Ross)
Thu Aug 9 13:28:24 2001
Date: Thu, 9 Aug 2001 13:25:02 -0400 (EDT)
From: Brandon Ross <bross@netrail.net>
To: Greg Pendergrass <greg@band-x.com>
Cc: "'Nanog@Merit. Edu'" <nanog@merit.edu>
In-Reply-To: <NHEFLBCNBEKGPCFNBKHJKEJBDAAA.greg@band-x.com>
Message-ID: <Pine.LNX.4.21.0108091314580.3013-100000@ogre.netrail.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On Wed, 8 Aug 2001, Greg Pendergrass wrote:
> The problem is if they aggregate and advertise only a /19 instead of
> individual /24s In this case you could:
>
> - Ask the pulverized ISP to withdraw the aggregate in favor of the specific
> /24s
> - Ask your second ISP to advertise your specific /24 in that city
Better yet, advertise your own /19 aggregate, mark your /24's with
communities that mean to your provider that they shouldn't be propagated
outside of their network and their customers (if they can't do this, fire
them) to be a good neighbor by not polluting the global routing table with
unnecessary routes. Then when the asteroid hits, just pull down the /19
advertisement (or if you're lucky, they are so destroyed they won't get
the announcement out to the world anymore anyway).
--
Brandon Ross 404-522-5400
EVP Engineering, NetRail http://www.netrail.net
AIM: BrandonNR ICQ: 2269442
Read RFC 2644!
