[1260] in North American Network Operators' Group

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

Re: Sprint BGP filters in 207.x.x.x?

daemon@ATHENA.MIT.EDU (Avi Freedman)
Wed Dec 13 15:06:06 1995

From: Avi Freedman <freedman@netaxs.com>
To: bmanning@isi.edu
Date: Wed, 13 Dec 1995 14:54:48 -0500 (EST)
Cc: jon@branch.com, dsiegel@rtd.com, cook@cookreport.com, dmbarton@mci.net,
        smd@chops.icp.net, nanog@merit.edu
In-Reply-To: <199512131939.AA02554@zed.isi.edu> from "bmanning@ISI.EDU" at Dec 13, 95 11:39:57 am

> > > Depends on the situation as to whether it's detrimental.  Proxy-aggregation,
> > > as this is called, can alter traffic patterns in dual-homed situations.  The
> > > change is not always bad, though it is often un-desirable.
> > > 
> > > In general, proxy-aggregation is good for everybody.
> > 
> > If we had a good method for people to indicate routes that they didn't want to
> > be aggregated, then more proxy aggregation could be done safely.
> > 
> 
> 	If I may...  The idea of using a routing registry for
> 	this purpose has been suggested before. I still think
> 	it is a valid approach.  Could be very useful in assisting
> 	with better proxy aggregation for all.
> 
> --bill

Here here.  This came up in response to an experiment on the
routing table (http://routes.netaxs.com).

But unless everyone uses an RR, it is not going to be a useful for building
proxy-aggregations on the fly (i.e. without human checking and intervention).

Avi


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