[27544] in North American Network Operators' Group
Re: More route-table bloat vs. ARIN micro-allocations
daemon@ATHENA.MIT.EDU (NANOG Mailing List)
Tue Feb 22 13:20:15 2000
Date: Tue, 22 Feb 2000 13:17:48 -0500 (EST)
From: NANOG Mailing List <nanog@EnterZone.Net>
To: Ulf Zimmermann <ulf@Alameda.net>
Cc: I Am Not An Isp <patrick@ianai.net>, nanog@merit.edu
In-Reply-To: <20000222091416.C45898@PacHell.TelcoSucks.org>
Message-ID: <Pine.LNX.3.96.1000222131236.32582A-100000@Overkill.EnterZone.Net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On Tue, 22 Feb 2000, Ulf Zimmermann wrote:
> > The point is, those /27s, /30s and /32s are *not* on the 'Net, they are
> > internal to C&W. You should not condemn the global table because C&W leaks
> > specifics to their customers.
>
> I am not connected directly to C&W, but via Exodus and I see the same
> routes like 63.84.242.192/26. So they not only inside of C&W and to their
> customers.
>
> --
> Regards, Ulf.
As we see 63.82.242.192:
*63.80.0.0/13
Neighbor: 209.115.127.21
Description: FNSI TRANSIT
ASPath: 6259 3549 701(IGP)
Nexthop: 209.115.127.21 Weight: 0
Localpref: 100
Last update: Tue Feb 22 11:31:39 2000
Sheesh folks. If your upstream isn't filtering at /24, you REALLY can do
it yourself. If it bothers you so much, contact whomever is leaking
prefixes longer than /24. Don't bitch and whine about it.
John Fraizer
