[j-nsp] BGP origination

[Richard A Steenbergen]

On Wed, Jan 29, 2003 at 12:33:49AM -0800, dre wrote:
> Don't mix customer prefixes with your own infrastructure addressing.
> Always save at least a few infrastructure addresses for customers,
> namely the preferrably /31 (but is often /30 due to code limitations)
> ptp links, and one loopback per customer (e.g. for bgp router-id per
> neighbor).  keep N for gre, hsrp/vrrp, and other off-one situations
> (plan accordingly; N is often larger with a smaller customer base).

You miss my point. Say a customer comes to you with their own /24, but
they don't speak BGP (it happens). You have to announce it for them, and
put it on an interface for them. If you want to use a static route for a 
holddown, you're either gonna be putting it on the interface as 2 /25s, or 
bust.

-- 
Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)