[2698] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Routes and routing tables

daemon@ATHENA.MIT.EDU (Avi Freedman)
Sun Apr 28 23:41:12 1996

From: Avi Freedman <freedman@netaxs.com>
To: paul@vix.com (Paul A Vixie)
Date: Sun, 28 Apr 1996 00:33:13 -0400 (EDT)
Cc: nanog@merit.edu
In-Reply-To: <9604280305.AA04191@wisdom.home.vix.com> from "Paul A Vixie" at Apr 27, 96 08:05:24 pm

> Sometimes more-specifics are needed to compete against more-specifics being
> incorrectly advertised by other people.  Sometimes folks _insist_ on cutouts,
> and you have to go route-to-route against them if you want to keep your block
> intact.  I hate this, it's bad business, I don't do it myself, I don't let my
> customers do it, but I've seen it often enough to have it be worth mentioning.

If you've got a larger block (say, a /16) and a customer with a /24 becomes
dual-homed and wants to split the incoming traffic on his links, you're
stuck advertising the /24 as well as the /16; otherwise, their 2nd provider
will always win for incoming traffic from most of the 'net...  However,
the 2nd path to a route consumes a LOT less memory than an additional
path.  

We do this for 1 customer right now, and possibly 1 in the near future.

Luckily, the demand for this is mostly limited to ISPs rather than 
other types of companies...

Avi


home help back first fref pref prev next nref lref last post