[1523] in North American Network Operators' Group
Re: Policy Statement on Address Space Allocations
daemon@ATHENA.MIT.EDU (Iljitsch van Beijnum)
Thu Jan 25 16:48:20 1996
From: Iljitsch van Beijnum <iljitsch@unix1.bart.nl>
To: smd@sprint.net
Date: Thu, 25 Jan 1996 22:29:46 +0100 (MET)
Cc: Daniel.Karrenberg@ripe.net, nanog@merit.edu, forrestc@imach.com,
cidrd@iepg.org, iab@isi.edu, iesg@isi.edu, iana@isi.edu,
local-ir@ripe.net, tli@cisco.com
In-Reply-To: <96Jan25.082047-0000_est.20608+303@chops.icp.net> from "Sean Doran" at Jan 25, 96 08:20:23 am
> Sure, there is no filtering in 193/8 and 194/8,
> and as a result we have VERY poor aggregation.
Get used to it. This is the Internet. People will not always do what
_you_ want.
> Consider this random cut-and-paste from 194/8.
>
> * 194.19.36.0 144.228.101.1 1 90 0 1239 701 3300 3301 5381 i
> * 194.19.37.0 144.228.101.1 1 90 0 1239 701 3300 3301 5381 i
> * 194.19.40.0 144.228.101.1 1 90 0 1239 701 3300 3301 5381 i
> * 194.19.54.0 144.228.101.1 1 90 0 1239 701 3300 3301 5381 i
> * 194.19.55.0 144.228.101.1 1 90 0 1239 701 3300 3301 5381 i
> * 194.19.60.0 144.228.101.1 1 90 0 1239 701 3300 3301 5381 i
> Putting in a filter on 195.0.0.0/8 that will permit ONLY
> /18s and shorter prefixes is the only means I can see at
> this time that will make this kind of b.s. impossible.
Yes. And of course you don't care about a small side-effect: it will
drive small ISP's out of business. The only way to avoid that is to do
business with large ISP's such as Sprint.
There are many legitimate reasons why people may announce very long
prefixes. I don't see a problem with that, as long as people aren't
announcing more routes than they have to.
So in stead of picking on people smaller than you, go after the types
that accounce 50+ routes per AS. That's the _real_ problem!
Iljitsch van Beijnum
bART Internet Services
