Route Reflector architecture and how to get small customer blocks in to BGP?
John van Oppen
john at vanoppen.com
Mon Jan 29 06:44:01 UTC 2007
Yep, that is a good strategy... No announcement without the right
communities sure makes it much harder to leak.
We redistribute lots of static routed stuff into BGP, but only announce
globally using network statements with route map applying the right
communities. So far, we have never leaked internal routes to
customers, peers or transit that we are aware of.
From: owner-nanog at merit.edu [mailto:owner-nanog at merit.edu] On Behalf Of
Sent: Sunday, January 28, 2007 1:12 PM
Subject: Re: Route Reflector architecture and how to get small customer
blocks in to BGP?
On Sun, Jan 28, 2007 at 10:59:50AM -0700, Danny McPherson wrote:
> o If you're going to use redistribution - or not - ensure that all
> external advertisement policies require explicit match of advertise
> communities and default is to deny
This should be just good security policy. I think of it as a
network-level instance of "that which is not expressly permitted
is denied" which everyone applies for services on their hosts,
RSUC / GweepNet / Spunk / FnB / Usenix / SAGE
More information about the NANOG